[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8355:
------------------------------------
we sure are!
XPaths was one of the things that really really were difficult for me to change and use
relative, and I kept delaying it. It would require really really heavy changes (last time
I checked, which I don't expect to have changed). I can give it another look of
course, but, yeah. XPaths was one of the things i evaluated and kept putting off as too
difficult.
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.2.1, 3.3.x
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