[ https://issues.jboss.org/browse/JBIDE-8517?page=com.atlassian.jira.plugin... ] Len DiMaggio updated JBIDE-8517: -------------------------------- Attachment: Screenshot.jpg -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8517?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-8517: ------------------------------------ It is actually important that the editor and toolset know what ports to interact with the server on. As you can see in the editor, your ports are not found. The box "Automatically detect" is checked, and yet the text box is empty. THis indicates that the toolset is *not* able to automatically detect these ports. How does hte toolset automatically detect the ports? It uses xpaths on specific files, and these xpaths are stored in an xpath model in the toolest. You can see in the screenshot, in the Servers view, an element under the server that reads "XML Configuration". XML configuration tracks xpaths and the values they resolve to. The toolset expects every AS server type to have specific XPaths available, and when creating a server via the New Server Wizard, or almost any other way, these xpaths should be automatically added for you by the toolset. Then, the editor checks these xpaths in order to find the ports to use when accessing JNDI, RMI, etc etc. In your screenshot, the "XML Configuration" node has zero children. This indicates an error in your toolset setup. Either you manually deleted the "Ports" section under the XML configuration, or, however your server was added, did not also add the required xml configuration details. So, I ask, how did you create this server object in your workspace? What were the steps used to create the server? Was it added upon JBDS installation? Did you install it simply via "New -> Server" ? Etc etc. Please outline these steps. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8517?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBIDE-8517: ------------------------------------------ Len, can we get some additional information on this one? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8517?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8517: -------------------------------------------- Len, any info on this ? -- 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

[ https://issues.jboss.org/browse/JBIDE-8517?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8517: -------------------------------------------- i.e. where can AS tooling team get the specific SOA-P server having problems here ? -- 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

[ https://issues.jboss.org/browse/JBIDE-8517?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8517: --------------------------------------- Priority: Critical (was: Minor) -- 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

[ https://issues.jboss.org/browse/JBIDE-8517?page=com.atlassian.jira.plugin... ] Len DiMaggio closed JBIDE-8517. ------------------------------- -- 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