[
https://issues.jboss.org/browse/JBDS-1974?page=com.atlassian.jira.plugin....
]
Rob Stryker resolved JBDS-1974.
-------------------------------
Resolution: Done
Changed jboss_config to jboss_config_dir and made some related changes to ensure that the
string replacement occurs before appending the runtime's location, since
jboss_config_dir will be a full path rather than a server-relative path.
CLONE - Server cannot be saved for the following reasons: One or more
ports have an invalid value
-------------------------------------------------------------------------------------------------
Key: JBDS-1974
URL:
https://issues.jboss.org/browse/JBDS-1974
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: servers
Affects Versions: 4.0.0.GA
Environment: I'm on Windows XP, Eclipse Indigo SR1, JBoss Tools 1.3.0 and JDK
1.6.0_29, JBoss 5.0.1GA
Reporter: Henri Tremblay
Assignee: Rob Stryker
Priority: Critical
Fix For: 5.0.0.M3, 4.1.0.CR2
I think I know how to reproduce. It occurs when the JBoss runtime is set to a directory
different from the default (server). If the name of the server you select doesn't
match one from the default servers, the port won't be resolved.
And I think the real reason is that the xpath of all the ports as a root directory to
"server/${jboss_config}". My guess is that it is wrong and should be
"D:\my_different_server_directory\${jboss_config}"
I also noticed that a tmp/jbosstoolsTemp dir is created in
"server/${jboss_config}" instead of
"D:\my_different_server_directory\${jboss_config}"
--
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