[
https://issues.apache.org/jira/browse/GERONIMO-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766627#action_12766627
]
David Jencks commented on GERONIMO-4909:
----------------------------------------
Configurations have more, or at least different, states than bundles expose
through BundleActivator:
||bundles||plugins||
|resolved|plugin installed|
|started|configuration gbean started|
|------|configuration gbeans started|
Whether starting the configuration gbean should automatically start the gbeans
in the configuration is stored in the load alse in config.xml. Normally,
stopping the configuration gbeans will indicate to geronimo that you want this
attribute set to "false".
If you stop a plugin bundle, you definitely want to stop the gbeans first.
However, if you are shutting down the server, you don't want to change the
attribute values.
In general we need a better way to deal with this extra state.
> How should we shut down plugin under osgi?
> ------------------------------------------
>
> Key: GERONIMO-4909
> URL: https://issues.apache.org/jira/browse/GERONIMO-4909
> 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.
