geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4909) How should we shut down plugin under osgi?
Date Mon, 19 Oct 2009 17:53:59 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767420#action_12767420
] 

Rick McGuire commented on GERONIMO-4909:
----------------------------------------

When a configuration bundle is constructed, are headers added to the manifest with important
metadata (such as the artifact id)?  This would make it fairly simple to determine this type
of mapping without needing to keep a side table of the information. 

> 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.


Mime
View raw message