[
https://issues.apache.org/jira/browse/GERONIMO-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767664#action_12767664
]
Shawn Jiang commented on GERONIMO-4909:
---------------------------------------
{quote}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.
{quote}
Can we just separate the (load=)attribute setting from the lifecycle ? IMO,
It's not a part of lifecycle, if the user want set (load=) to true/false, there
should be explicitly API to call but not just an indicating action during
config stop lifecyle.
> 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.
