[
https://issues.apache.org/jira/browse/FELIX-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho updated FELIX-4598:
----------------------------------
Component/s: Dependency Manager
Affects Version/s: dependencymanager.runtime-3.2.0
> BundleDependency can effectively track only one bundle
> ------------------------------------------------------
>
> Key: FELIX-4598
> URL: https://issues.apache.org/jira/browse/FELIX-4598
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
> Affects Versions: dependencymanager.runtime-3.2.0
> Reporter: Tuomas Kiviaho
>
> Bundles are delivered to callbacks after component is instantiated but prior
> to that they can't be. This is the case with ServiceDependencies as well but
> unlike them after component instantiation the tracker is not used as source
> of bundles but instead lookup method is used. ServiceDependencyImpl uses this
> approach only to gain properties and auto configuration instance.
> I suggest that BundleDependencyImpl#invokeAdded(DependencyService service)
> would be implemented in similar manner that
> ServiceDependencyImpl#invokeAdded(DependencyService service) has been
> (perhaps also utilizing the serial executor) and lookupBundle() would utilize
> tracker first as does lookupService().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
