[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.

[ http://jira.jboss.com/jira/browse/JBIDE-2050?page=comments#action_12410624 ] Rob Stryker commented on JBIDE-2050: ------------------------------------ Ok my last message was innaccurate. This is interesting. I had never used that specific feature of JBoss before. So... when trying to startup / shutdown, the tooling needs to know the JNDI port... The question ultimately is how to find it. It is usually hard-coded in jboss-service.xml, and that's where the tooling would usually find it. You, however, have made use of the service binding feature. Rather than editing these ports directly in the jboss-service.xml, you've kept them in another file in a named configuration. As of now, here's the best work-around I can offer you, which is actually pretty damn good! So, for the sake of example, let's call my new configuration "testConfig". The first thing I did was open server/testConfig/conf/jboss-service.xml and modify the store url to make sure the store file would be somewhere in testConfig. <mbean code="org.jboss.services.binding.ServiceBindingManager" name="jboss.system:service=ServiceBindingManager"> <attribute name="ServerName">ports-01</attribute> <attribute name="StoreURL">${jboss.home.url}/server/testConfig/conf/sample-bindings.xml</attribute> <attribute name="StoreFactoryClassName"> org.jboss.services.binding.XMLServicesStoreFactory </attribute> </mbean> The next thing I did was, in the JBoss Servers View, select my server, and in the lower half, browse into XML Configuration -> Ports. In the properties view, you should see one that says "JNDI". Right-click on that and select "Delete XPath". Then right-click in the same area and select "New XPath". The XPath's name ***must*** be JNDI The XPath's pattern should be //service-bindings/server[@name='ports-01']/service-config[@name='jboss:service=Naming']/binding And in the "Attribute Name" field, put "port" What this is basically doing is it's telling the tooling NOT to look in jboss-service.xml for the JNDI port anymore, but to instead look in the new XPath. It should find the real port there. (The reason we had to delete and re-create the xpath rather than modify is that the xpath UI does not currently display another field which limits the searching for the xpath to one specific file.) I realize this is a little convoluted. I'll leave the bug opened but modify it so that it's a feature request to add support for service bindings more easily. Hope this helps! Post here if you need any further assistance! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira