geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4909) How should we shut down plugin under osgi?
Date Fri, 16 Oct 2009 08:28:31 GMT


Ivan commented on GERONIMO-4909:

>From the beginning, we are trying to match the Configuration lifecycle to the bundle lifecycle,
it brought us too much issues. Since currently Geronimo Kernel is still there, shall we treat
them separately. 
While starting the bundle, preload the ConfigurationData, the most reason to do this is for
having a chance to mantaine an artifactid -> bundleContext map, if there is another way
to do it, we would do nothing.
While the bundle is active, we could do any configuration lifecycle operations, it will not
affect the bundle's status, it only changes Geronimo repository.
While stopping the bundle, we also stop/unload the configuration.
While uninstalling the bundle, we will missing  :-)

> How should we shut down plugin under osgi?
> ------------------------------------------
>                 Key: GERONIMO-4909
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: David Jencks
> 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