[jbosstools-issues] [JBoss JIRA] (JBIDE-11057) why is configuration file relative to standalone/configuration instead of server home !?

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-11057.
---------------------------------

    Resolution: Rejected


It is stored relative to standalone/configuration because that's how the jboss application server handles it. For example, the command

     ./standalone.sh -b localhost --server-config=standalone/configuration/standalone-full.xml

Will fail, while the command

    ./standalone.sh -b localhost --server-config=standalone-full.xml

Will succeed. 

The error from launching will be something like:

14:37:57,236 INFO  [org.jboss.modules] JBoss Modules version 1.1.0.CR8
java.lang.IllegalStateException: JBAS014805: Could not get main file: standalone/configuration/standalone-full.xml. Specified files must be relative to the configuration dir: /home/rob/apps/jboss/unzipped/jboss-as-7.1.0.Final-SNAPSHOT/standalone/configuration

This is why the configuration file is stored relative to standalone/configuration instead of server home. 
                
> why is configuration file relative to standalone/configuration instead of server home !?
> ----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-11057
>                 URL: https://issues.jboss.org/browse/JBIDE-11057
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS/Servers
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.Beta1, 3.3.0.CR1
>
>
> The AS 7.1 server seem to have the configuration xml file be relative to <ashome>/standalone/configuration instead of <ashome>
> Why ?
> Users should be able to point to domain/configuration/xyz.xml too.

--
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