Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
org.apache.felix.dependencymanager-r1
-
None
Description
Surprisingly, a regression has been done in dm4, before releasing the first version:
In ComponentImpl.java, before the commit from revision 1640812, service references were properly ungotten when a DM component was stopped (using DependencyManager.remove(Component) method).
But since rev 1640812, when you programmatically remove a DM component, then any service references hold by the ServiceDependencies are not ungotten anymore.
I have a test case which reproduces this issue.