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:05:58 UTC
[jira] [Resolved] (FELIX-5411) When you stop a component, the
service references are not ungotten.
[ https://issues.apache.org/jira/browse/FELIX-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre De Rop resolved FELIX-5411.
----------------------------------
Resolution: Fixed
Committed the org.apache.felix.dependencymanager.itest/src/org/apache/felix/dm/itest/api/UngetServiceTest.java in revision 1769553.
Committed the fix in revision 1769554.
> 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)