[jboss-jira] [JBoss JIRA] Created: (JBAS-6708) once DeploymentManager.stop() is called on a WAR deployment, the next time managementView.getDeploymentNamesForType("war") is called, a deployment is no longer returned for that WAR

[Ian Springer (JIRA)]

once DeploymentManager.stop() is called on a WAR deployment, the next time managementView.getDeploymentNamesForType("war") is called, a deployment is no longer returned for that WAR
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBAS-6708
                 URL: https://jira.jboss.org/jira/browse/JBAS-6708
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: ProfileService
            Reporter: Ian Springer
            Assignee: Emanuel Muckenhuber


The deployment should still be returned, since the WAR is still deployed and just in the Stopped state. 

The fact that it is not returned causes it to give removed from the Admin Console's inventory (since our discovery scan calls managementView.getDeploymentNamesForType("war") to determine the currently deployed WARs) , which means if a user stops a WAR via the Admin Console, they will have no way to restart that same WAR using the Admin Console.


-- 
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