[
https://jira.jboss.org/jira/browse/JBAS-6701?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber commented on JBAS-6701:
-------------------------------------------
Yes, copyContent=false won't remove the deployment itself - as in this case the
deployment is intended to come from 'outside AS'. Therefore it will never try to
actually delete the deployment it just removed it's reference on the server.
And yes, remove() won't stop the deployment - it just removes the deployment, but it
could still exist in the temp dir. Which means that stop() and remove() have to be called
to fully undeploy and remove a deployment.
DeploymentManager.remove() doesn't work
---------------------------------------
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: Critical
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