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

[jira] Closed: (GERONIMO-1295) Deploy & Undeploy no longer affect config.xml; next startup dies

     [ http://issues.apache.org/jira/browse/GERONIMO-1295?page=all ]
     
Dain Sundstrom closed GERONIMO-1295:
------------------------------------

    Resolution: Fixed

I needed to call attributeChanged in addConfiguration, removeConfiguration and setReference.

Sending        trunk/modules/system/src/java/org/apache/geronimo/system/configuration/LocalAttributeManager.java
Transmitting file data .
Committed revision 354878.

> Deploy & Undeploy no longer affect config.xml; next startup dies
> ----------------------------------------------------------------
>
>          Key: GERONIMO-1295
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1295
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Assignee: Dain Sundstrom
>     Priority: Blocker
>      Fix For: 1.0

>
> I just updated, and now if I deploy an app it is not written to config.xml, and if I undeploy an app it is not marked as disabled.  Therefore after undeploying, the server won't start any more because config.xml refers to configurations that are no longer in the config store.
> to reproduce:
>  - Build modules/assembly
>  - Start the server
>  - Run  java -jar target/geronimo-1.0-SNAPSHOT/bin/deployer.jar undeploy geronimo/console-jetty/1.0-SNAPSHOT/car
>  - Stop the server
>  - Start the server -- it dies during startup

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