You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/12/10 10:38:08 UTC

[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

     [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Aaron Mulder updated GERONIMO-1285:
-----------------------------------

    Fix Version: 1.1
                     (was: 1.0)

Seems like it would need a fairly extensive change for Configuration or Kernel calls to return a list of GBeans or Configurations that were stopped, so that the ConfigurationManagerImpl could return a list of Configurations that were stopped, so that the JSR-88 impl could list them in the progress object.

> Deployer does not list all modules that have been stopped
> ---------------------------------------------------------
>
>          Key: GERONIMO-1285
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1285
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>      Fix For: 1.1

>
> When you, for example, stop the "tomcat" configuration, all the web apps deployed to Tomcat are stopped too.  However, the deployer does not let you know this.  It should list all modules that were stopped, just like it does when starting.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira