[jboss-jira] [JBoss JIRA] Resolved: (JBAS-6701) DeploymentManager.remove() doesn't work for exploded apps that were deployed via distribute(copyContent=false)
Ian Springer (JIRA)
jira-events at lists.jboss.org
Tue Apr 14 12:21:39 EDT 2009
[ https://jira.jboss.org/jira/browse/JBAS-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Springer resolved JBAS-6701.
--------------------------------
Resolution: Won't Fix
Emanuel said remove() not working for apps that were deployed with the copyContent=false option is expected, behavior, so I am resolving this as Won't Fix. This will no longer be an issue once https://jira.jboss.org/jira/browse/JBAS-6693 has been implemented.
> DeploymentManager.remove() doesn't work for exploded apps that were deployed via distribute(copyContent=false)
> --------------------------------------------------------------------------------------------------------------
>
> 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: Ian Springer
> Priority: Critical
> Fix For: JBossAS-5.1.0.CR1
>
>
> 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
More information about the jboss-jira
mailing list