You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Pierre De Rop (JIRA)" <ji...@apache.org> on 2016/11/13 22:03:59 UTC

[jira] [Created] (FELIX-5411) When you stop a component, the service references are not ungotten.

Pierre De Rop created FELIX-5411:
------------------------------------

             Summary: When you stop a component, the service references are not ungotten.
                 Key: FELIX-5411
                 URL: https://issues.apache.org/jira/browse/FELIX-5411
             Project: Felix
          Issue Type: Bug
          Components: Dependency Manager
    Affects Versions: org.apache.felix.dependencymanager-r1
            Reporter: Pierre De Rop
            Assignee: Pierre De Rop
             Fix For: org.apache.felix.dependencymanager-r9


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)