[
https://issues.jboss.org/browse/JBDS-1974?page=com.atlassian.jira.plugin....
]
Henri Tremblay updated JBDS-1974:
---------------------------------
Description:
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}"
was:
Bug is similar to what's described in JBIDE-5263. The user goes to save artifacts he
is given a dialogue with the text "Server cannot be saved for the following reasons:
One or more ports have an invalid value".
This ticket differs from JBIDE-5263 in that the user is a Windows user, not Mac.
Environment: I'm on Windows XP, Eclipse Indigo SR1, JBoss Tools 1.3.0
and JDK 1.6.0_29, JBoss 5.0.1GA (was: JBDS running with a SOA-P server)
Workaround Description: Have a copy of your bindings.xml file in
"server/${jboss_config}/conf/bootstrap"
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: 4.1.0.CR2, 5.0.0.M3
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