[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5931) Renaming deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-5931:
------------------------------------
Interestingly, this is an expected use case in WTP nad they have project refactor
listeners ot handle this.
However, a quick trace reveals... (... ... ...) that they don't work all that great
;)
I'll get to testing nad patching I guess
Renaming deployed project on running server results in the project to
be deployed twice
---------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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