[
https://issues.apache.org/jira/browse/FELIX-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207121#comment-14207121
]
Jens Kübler commented on FELIX-3557:
------------------------------------
I have a probably related case and I am unsure if this is fixed by this issue:
I have two components that both mandatory require component A. The sequence is
1. ConsumerA#bind(A)
2. Scr Instantiates A via ServiceUse#getService
3. A has no dependencies and is instantiated
4. A bundle event occurs firing newly enabled components to resolve
5. ConsumerB is immediate and synchrnously binds via ConsomerB#bind(A) since A
is now available
6. Scr tries to retrieve the Service again via ServiceUse#getService
Since this all happens in the same stack, I get a circularity problem where I
would not expect one.
I suspect loading this or another component triggered the bundle event causing
the circularity.
Is this a new problem or is it solved by the fix ?
> Tests for DS circular dependency behavior
> -----------------------------------------
>
> Key: FELIX-3557
> URL: https://issues.apache.org/jira/browse/FELIX-3557
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.6.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: scr-1.6.2
>
> Attachments: FELIX-3557-add-missing-refs-later.diff,
> FELIX-3557-circ-dep-later-2.diff
>
>
> The DS spec is pretty confused about circular dependencies between DS
> services. I wrote some tests to try to make better sense of the situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
