[
https://jira.jboss.org/jira/browse/JBIDE-3391?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-3391.
--------------------------------
Resolution: Rejected
In this specific example, the user forgot to save the dirty server editor.
Changing a runtime name also changes it's ID. This was a decision made many months ago
to attempt to facilitate the sharing of server objects that reference runtimes by name
rather than some obscure ID.
The renaming of runtimes now causes all sorts of problems. By changing the name, we
currently change the ID to keep the two in sync. Looking back, changing a runtime or
server's ID is probably a bad idea and may need to be revisited.
Either way, I mark this bug currently as closed, as the surrounding issues are not
directly related to this. This specific JIRA is a user error. The user did not save a
dirty editor.
Can't deploy/undeploy project to the server if name of the
server's runtim was changed.
---------------------------------------------------------------------------------------
Key: JBIDE-3391
URL:
https://jira.jboss.org/jira/browse/JBIDE-3391
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.cr1
Reporter: Anton Klimkovich
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.0.0.CR2
Attachments: exception.txt
EXECUTE: Create new seam web project
EXECUTE: Publish it to the JBoss AS
EXECUTE: Properties->Server -> Runtime Environments
EXECUTE: Press Edit button and change name of Server runtime
EXECUTE: Open JBoss Server View
EXECUTE: Open Add and remove Projects wizard
EXECUTE: Remove added seam project and press Finish button
FAILURE: java.lang.reflect.InvocationTargetException is occured.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira