[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Cernich commented on JBIDE-8355:
------------------------------------
I don't know if this is related (or should be a new issue), but another thing I've
noticed is that the jar files in the library entries (e.g. JBoss ESB Runtime, JBoss
Enterprise Application Platform) point to the "default" jars instead of the
specified configuration's jars.
My workaround: (I don't know if the first step is necessary)
1. update the runtime: select a different config, then the desired config, press finish.
2. close the project
3. open the project
4. the jars listed in the library are now from the desired configuration
Automatic detection of server ports cannot handle changing
configuration from default
-------------------------------------------------------------------------------------
Key: JBIDE-8355
URL:
https://issues.jboss.org/browse/JBIDE-8355
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Rob Stryker
Fix For: 3.3.0.M2
I create a new server for JBoss AS 6.0.
I select the "default" configuration in the "New server" dialog.
JNDI port is detected as 1099 as it should be.
Now i open the "Edit server runtime environment" dialog and change from
"default" to "all" configuration.
I have edited the conf/bindingservice.beans\META-INF\bindings-jboss-beans.xml file to use
JNDI port 11099 instead of 1099 for the "all" configuration.
Now the autodetected JNDI port is still 1099?
If i click the "Configure..." next to the auto detect checkbox and then
"Edit XPath" i see that the root directory is still pointing to the default
configuration.
If i click the browse button and try to change the root directory it does not take the
change. It still points to the default directory the next time i open the "Edit
XPath" dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira