geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Resolved: (GERONIMO-1483) During Undeploy entry in config.xml is not removed
Date Thu, 08 Jun 2006 03:27:30 GMT
     [ ]
Aaron Mulder resolved GERONIMO-1483:

    Resolution: Invalid

The current (near-1.1) behavior if you uninstall B is that A is stopped, B is uninstalled,
and the entries for both A and B in config.xml are marked as load=false.  B is no longer listed
(e.g. in the console) as available, though A is.  If you then try to start A, it fails with
a lifecycle failure caused by a missing dependency exception.  But if you install B again,
then both A and B can be started as expected.

While this does not have the effect that the submitter seems to be after (both A and B uninstalled
and config.xml entries deleted), I think it's correct, and therefore this is not really an

> During Undeploy entry in config.xml is not removed
> --------------------------------------------------
>          Key: GERONIMO-1483
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: console, deployment
>  Environment: WinXP, JDK1.4.2_09 X86 Intel
>     Reporter: Manu T George
>     Assignee: Aaron Mulder
>     Priority: Critical
>      Fix For: 1.1

> Suppose I have two modules A and B and A is dependant  on B. Usually we first remove
A and then  B . This works fine. If we remove B and then A then the entry in config.xml is
not removed and the server does not allow me to again deploy the module A. This problem was
noticed on running the deploy command. from console

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message