[ https://issues.jboss.org/browse/JBDS-1677?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-1677: -------------------------------------- Fix Version/s: 4.1.0.CR2 5.0.0.M3 Priority: Critical (was: Major) Assignee: Rob Stryker Component/s: servers (was: integration) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1677?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-1677: ----------------------------------- As has been mentioned, xpaths are used to locate ports that the tooling needs to interact with the app server. Should the installed app server be incorrectly configured, be missing critical descriptor files, or simply be of a different version / layout, these expected files or xpaths may not be found. In the event the user has purposely customized his configuration to something non-standard, the user can either click "configure" on that section of the editor, and select (or create) a new xpath to match where the user has put the desired ports. It is also possible that the user deleted the xpath, not in the actual server configuration, but rather in the toolset. You can see these xpaths by expanding your server in the Servers view and seeing an "XML Configuration" section, under which should be a category called "PORTS" and under that, items such as "JNDI" or "WEB" etc etc etc. It is possible the user deleted these critical xpaths. Should, for whatever reason, teh xpath not be found, odds are it is an error in the setup of the actual app server, as the files are in standard locations and with non-changing xpaths, however, the user still has the option to UNCHECK "detect automatically" and instead directly input a port number that the toolset should use when attempting to interact with the server. Under no circumstances is it acceptable that a null port be used. The tooling must always know one way or another what the web / jndi / etc ports are. Either it can detect them automatically, or, the user can hand-enter the port the toolset should use. Therefore, it is not an error that an attempt to save a Server Editor that cannot locate it's proper ports. This is by design. If the toolset cannot locate the proper ports, the user must instead manually declare them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1677?page=com.atlassian.jira.plugin.... ] Rick Wagner updated JBDS-1677: ------------------------------ Attachment: JBDS_Ports.png Picture attached for future reference for viewers of this JIRA. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1677?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-1677: ------------------------------ Attachment: JBDS-1677_v2.png If the user clicks on "Configure...", a dialog will pop up. This dialog will list all defined PORT xpaths on the left, and the value they resolve to on the right. If the user then clicks "Edit XPath", another dialog will appear, and this dialog will list all the xpath details. The user should then click "preview" to see the result. If the first dialog has no xpaths, that's the problem. No xpaths means the port must be manually declared and the server was incorrectly created (or, afterwards, modified in a bad way). If the xpaths are all present in the first dialog, but the value on the right is wrong, then that means either the xpath was changed somehow, or, the user changed the value in the actual xml file. If all xpaths are present, and the xpaths all resolve to actual values, then this error quite simply should NOT be occurring. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1677?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-1677. ------------------------------- Closing this JIRA as it cannot be reproduced. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira