You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2010/04/07 16:05:40 UTC
[jira] Commented: (GERONIMO-4909) How should we shut down plugin
under osgi?
[ https://issues.apache.org/jira/browse/GERONIMO-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854508#action_12854508 ]
Ivan commented on GERONIMO-4909:
--------------------------------
Not sure whether we have conclusion for this, I would like to add the operations of removing bundle in the unloadConfiguration method first, for currently, while undeploying the applcations, the bundle is still there. Thoughts ?
> How should we shut down plugin under osgi?
> ------------------------------------------
>
> Key: GERONIMO-4909
> URL: https://issues.apache.org/jira/browse/GERONIMO-4909
> 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.