[
https://issues.apache.org/jira/browse/FELIX-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695545#comment-15695545
]
Pierre De Rop commented on FELIX-5426:
--------------------------------------
Dobias,
I committed a quick patch in revision 1771275.
I have to go to now, but I will reconnect later today and will get back to you
to explain more about the issue.
in the meantime, can you could give a shot to the trunk to see if your issue is
fixed ?
PS: I did not have time to analyze and test your sample code but will do it
today;
many thanks.
> Remove callbacks aren't called for optional dependencies in a "circular"
> dependency scenario
> --------------------------------------------------------------------------------------------
>
> Key: FELIX-5426
> URL: https://issues.apache.org/jira/browse/FELIX-5426
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
> Affects Versions: org.apache.felix.dependencymanager-r8
> Reporter: Dobias van Buuren
> Assignee: Pierre De Rop
> Attachments: Activator.java
>
>
> In some cases, the whiteboard pattern remove callbacks aren't called by the
> depenency manager.
> See attached test class. Here some sort of "cyclic" dependency is made
> between 'Shop' -> 'Item' -> 'Shop'.
> See the log when starting and stopping a bundle with the attached
> Activator.java for an example.
> Some investigation pointed us to ComponentImpl line 1191:
> {code}
> if (dc.isRequired()) {
> invokeCallbackSafe(dc, EventType.REMOVED, e);
> }
> {code}
> When removing the condition for the required dependency, the REMOVED
> callbacks are called!
> Why is the above condition written in the ComponentImpl.java? Can you please
> investigate this?
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
