[jboss-jira] [JBoss JIRA] (AS7-784) Remove deployment doesn't really remove it
[
https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.sy...
]
Stan Silvert reopened AS7-784:
------------------------------
In that case, I think we need to go back to Brian's original comment and throw an
error if you try to remove a file-managed deployment via a management operation.
As it is now, there is no way for the console to know if a deployment can be removed or
not. It's really not such an edge case to think that a user will see the deployment
in the console and try to remove it.
Remove deployment doesn't really remove it
------------------------------------------
Key: AS7-784
URL: https://issues.jboss.org/browse/AS7-784
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Beta3
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: No Release
Steps:
1) Deploy something by copying an archive to the standalone/deployments directory.
2) Using the CLI or Console, remove the deployment.
i.e. /deployment=mywar.war/:remove
The deployment will stop, but the .war file and .deployed marker remain on the file
system. When you restart the server, mywar.war will deploy again.
The problem is that "remove" doesn't really remove. It only stops the
deployment until the next full restart. If you try to do some other operation on the
deployment you will get a NoSuchElementException.
And from the file system, it looks like the deployment is still deployed.
So we need to do something to fully "remove" the deployment. Perhaps we need
(yet another) marker file called .removed
--
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