geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <>
Subject [jira] Updated: (GERONIMO-4909) How should we shut down plugin under osgi?
Date Mon, 01 Feb 2010 18:26:18 GMT


Rick McGuire updated GERONIMO-4909:

    Issue Type: Sub-task  (was: Bug)
        Parent: GERONIMO-5087

> How should we shut down plugin under osgi?
> ------------------------------------------
>                 Key: GERONIMO-4909
>                 URL:
>             Project: Geronimo
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: David Jencks
>             Fix For: 3.0
> ConfigurationActivator needs it's stop method to shut down the plugin.
> Calling configurationManager.unload(id) is symmetrical with start and should leave the
configuration model in a consistent state, but resets the load attribute in config.xml to
false, which prevents restarting the server.
> Just stopping and unloading the configuration gbean works fine but may leave the configuration
model (in the configuration manager) in an inconsistent state.
> This needs further investigation.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message