[jbosstools-issues] [JBoss JIRA] (JBIDE-11267) Remote Configuration, Runtime Server config missing field "Remote Configuration"

[Martin Malina (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-11267.
---------------------------------



OK, but since I cannot verify this in Beta3, I made a note to myself in the other JIRA to verify this when verifying that JIRA :)
Closing this issue.
                
> Remote Configuration, Runtime Server config missing field "Remote Configuration"
> --------------------------------------------------------------------------------
>
>                 Key: JBIDE-11267
>                 URL: https://issues.jboss.org/browse/JBIDE-11267
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>            Reporter: Leo Breuss
>            Assignee: Rob Stryker
>              Labels: RSE, runtime
>             Fix For: 3.3.0.Beta3
>
>         Attachments: standalone-custom-in-server-editor.png
>
>
> In the JBoss Runtime Server configuration, I am no longer able to specify the Remote Configuration (e.g. standalong-full.xml). It seems like this field has been dropped between 20111208 and today's 3.3.0b2.
> In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the problems disucussed in the Forum Reference.
> 1. The path on the server to look for the existence of the configuration was the concatenation of <Remote Server Home> + "/server/" + <Remote Server Configuration>. But JBoss 7 has a different layout structure. No /server/ directory.
> 2. In the field "Remote Configuration" you should be able to select the appropriate configuration file from the remote server file system. (Interestingly enough, the field Remote Server Home can be set by browsing the remote file system.) Instead, one could browse for a local configuration file, but had to manually strip the absolute path. Only the filename may remain, because of the concatenation. And the local JBoss installation has to reflect the remote JBoss regarding the configuration file names. The default value "default" did not work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira