[
https://issues.apache.org/jira/browse/FELIX-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop closed FELIX-4168.
--------------------------------
Resolution: Invalid
Hi Angelo,
I'm closing this old issue, since using setInstanceBound() method is fixing the
problem.
Notice that in the upcoming DM4, we have removed the setInstanceBound() method,
which has been removed from the API.
I also added you testcase in [1] (thanks !).
[1]
http://svn.apache.org/viewvc/felix/sandbox/pderop/dependencymanager-prototype/org.apache.felix.dependencymanager.itest/src/org/apache/felix/dm/itest/FELIX_4168AdapterWithDynamicallyAddedDependencies.java
> Adapter services don't call callbacks for existing services when adding a
> required dependency after setup
> ---------------------------------------------------------------------------------------------------------
>
> Key: FELIX-4168
> URL: https://issues.apache.org/jira/browse/FELIX-4168
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
> Affects Versions: dependencymanager-3.1.0
> Reporter: Angelo van der Sijpt
> Attachments: FELIX_4168AdapterWithDynamicallyAddedDependencies.java
>
>
> I have the following scenario,
> - an adapter service comes up for some underlying service;
> - some time during start (either during init(), start(), or add()), I add a
> required service dependency, with callbacks;
> - the service on which we depend, is already available.
> I would expect the callbacks get called during startup of the component.
> However, this doesn't happen.
> I have been able to localize this a little further,
> - this only happens when the service is already available (i.e., services
> that show up later work fine),
> - the service does not get pulled because of the new dependency (which is
> should),
> - it doesn't matter which callback function I register the depencies from,
> - it can be solved partially by setting the required dependencies to be
> instanceBound(), but then still the service doesn't get pulled before a
> service becomes available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
