[ https://jira.jboss.org/browse/JBIDE-6716?page=com.atlassian.jira.plugin.s... ] Burr Sutter updated JBIDE-6716: ------------------------------- Attachment: stopping_EAP.png -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6716?page=com.atlassian.jira.plugin.s... ] Rob Stryker resolved JBIDE-6716. -------------------------------- Assignee: Rob Stryker Fix Version/s: (was: 3.2.x) Resolution: Rejected I've looked into this about a year ago but the fact is it would be very very very difficult for me to properly handle this situation. The shutdown script depends on JNDI's port, and currently we have two ways for the user to set which port to use. The first way is for the user to open the server editor and uncheck the "Automatically detect" box for JNDI port, which would allow him to hard-code what jndi port he's using. The second way is to scan using an xpath. These are the only two ways currently to do it. Either you hard-code it, or you use an xpath. The xpath currently being used for automatic detection is the following beast: /deployment/jboss_bean-deployer_2:bean/jboss_bean-deployer_2:constructor/jboss_bean-deployer_2:parameter/jboss_bean-deployer_2:set/jboss_bean-deployer_2:bean[jboss_bean-deployer_2:property='jboss:service=Naming' and jboss_bean-deployer_2:property='Port']/jboss_bean-deployer_2:property[@name='port'] The beans file works using offsets, and changing from ports-default to ports-01 basically adds 100 to the port. In order for me to properly handle this, I'd need to first scan which bindings are currently being used, then check what the port offset for it is, then check the default one, then add them together, etc. This is quite simply impossible for the current API of using an XPath. It would require another abstraction level added in. This would be troublesome on its own, but then the question is how to represent this automatic scanner via UI. I'm just going to go ahead and reject this one. The amount of work it would require on things (both API and UI) that are fairly settled would be very disruptive for very little gain. If the user wants to override the ports when starting the server, he should change the launch configuration to show that, and then change the server's JNDI port as described in the server editor. Sorry -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira