[
https://issues.apache.org/jira/browse/GERONIMO-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767423#action_12767423
]
Rick McGuire commented on GERONIMO-4909:
----------------------------------------
I think the blueprint model maps pretty closely to what's going on here, with
the addition of being able to explicitly start/stop the Gbean context of a
given bundle. With the blueprint model, a bundle can have the states stopped,
started with BlueprintContainer active, and started with no Blueprint Container
active. The last state can only occur if there is a startup error or the
extender is shutdown. I think it makes a lot of sense to allow the framework
to manage the bundle state, and the Geronimo kernel (extender?) manage the
configuration state as separate entities.
> 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
> 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.
