[jboss-jira] [JBoss JIRA] Commented: (AS7-784) Remove deployment doesn't really remove it

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602163#comment-12602163 ] 

Brian Stansberry commented on AS7-784:
--------------------------------------

I'd rather just have the CLI operation fail (or be unavailable), if there was a clean way to do it. If you're using the FS scanner to manage your deployments, you're turning over management of the deployment to the scanner.

There's probably not a clean way to do it though. :(

> 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
>    Affects Versions: 7.0.0.Beta3
>            Reporter: Stan Silvert
>            Assignee: Brian Stansberry
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira