You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/09/06 10:16:31 UTC
[jira] Created: (FELIX-355) ConfigurationAdmin service is
unregistered after it has been cleaned up
ConfigurationAdmin service is unregistered after it has been cleaned up
-----------------------------------------------------------------------
Key: FELIX-355
URL: https://issues.apache.org/jira/browse/FELIX-355
Project: Felix
Issue Type: Bug
Components: Configuration Admin
Reporter: Felix Meschberger
Fix For: 1.0.0
The ConfigurationManager as the BundleActivator of the Configuration Admin implementation shuts down and cleans up in the stop(BundleContext) method and leaves unregistration of the service to the framework. This causes potential issues in active environments, where the ConfigurationAdmin service may still be used albeit it has already been clean up.
The ConfigurationManager.stop method should actually unregister the service before cleaning up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-355) ConfigurationAdmin service is
unregistered after it has been cleaned up
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned FELIX-355:
---------------------------------------
Assignee: Felix Meschberger
> ConfigurationAdmin service is unregistered after it has been cleaned up
> -----------------------------------------------------------------------
>
> Key: FELIX-355
> URL: https://issues.apache.org/jira/browse/FELIX-355
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 1.0.0
>
>
> The ConfigurationManager as the BundleActivator of the Configuration Admin implementation shuts down and cleans up in the stop(BundleContext) method and leaves unregistration of the service to the framework. This causes potential issues in active environments, where the ConfigurationAdmin service may still be used albeit it has already been clean up.
> The ConfigurationManager.stop method should actually unregister the service before cleaning up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-355) ConfigurationAdmin service is
unregistered after it has been cleaned up
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-355.
-----------------------------------
Resolution: Fixed
Fixed in Rev. 573174 and also deployed a new snapshot 20070906.081947-8
> ConfigurationAdmin service is unregistered after it has been cleaned up
> -----------------------------------------------------------------------
>
> Key: FELIX-355
> URL: https://issues.apache.org/jira/browse/FELIX-355
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 1.0.0
>
>
> The ConfigurationManager as the BundleActivator of the Configuration Admin implementation shuts down and cleans up in the stop(BundleContext) method and leaves unregistration of the service to the framework. This causes potential issues in active environments, where the ConfigurationAdmin service may still be used albeit it has already been clean up.
> The ConfigurationManager.stop method should actually unregister the service before cleaning up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (FELIX-355) ConfigurationAdmin service is
unregistered after it has been cleaned up
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-355 started by Felix Meschberger.
> ConfigurationAdmin service is unregistered after it has been cleaned up
> -----------------------------------------------------------------------
>
> Key: FELIX-355
> URL: https://issues.apache.org/jira/browse/FELIX-355
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 1.0.0
>
>
> The ConfigurationManager as the BundleActivator of the Configuration Admin implementation shuts down and cleans up in the stop(BundleContext) method and leaves unregistration of the service to the framework. This causes potential issues in active environments, where the ConfigurationAdmin service may still be used albeit it has already been clean up.
> The ConfigurationManager.stop method should actually unregister the service before cleaning up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.