[
https://jira.jboss.org/jira/browse/JBAS-6701?page=com.atlassian.jira.plug...
]
Ian Springer commented on JBAS-6701:
------------------------------------
I first deploy the EAR in exploded form using the Admin Console, which, under the covers:
1) extracts the EAR file to deploy/foo.ear.rej/
2) renames foo.ear.rej/ to foo.ear/
3) calls DeploymentManager.distribute() on foo.ear/, specifying copyContent=false
I then try to undeploy it via the Admin Console, which, under the covers, simply:
- calls DeploymentManager.remove(), passing foo.ear's ManagedDeployment
The call to remove() indicates successful completion, yet the deploy/foo.ear/ dir still
exists and the corresponding ManagedDeployment is still reported.
DeploymentManager.remove() doesn't work when the application is
deployed in exploded form
------------------------------------------------------------------------------------------
Key: JBAS-6701
URL:
https://jira.jboss.org/jira/browse/JBAS-6701
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Priority: Minor
deploymentManager.remove() reports success [1]. Peeking under the covers, the directory
corresponding to the app does get deleted. However,
managementView.getDeployment(deploymentName) still returns the deployment, even after
refreshing the view.
[1] Side Note: Actually both isRunning() and isCompleted() return true, which doesn't
seem right.
--
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