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.
