[jira] [Resolved] (FELIX-4598) BundleDependency can effectively track only one bundle

["Pierre De Rop (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre De Rop resolved FELIX-4598.
----------------------------------

    Resolution: Fixed

issue resolved in dm 4.0.0

Tuomas, I will see with Marcel/Xander if we can move the dm 4.0.0 sandbox in the felix-trunk. If this is not possible to do it quickly, then I'll look at your proposed patch and will commit it in the trunk (but when I will get back from vacations); 
thanks.

> 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
>            Assignee: Pierre De Rop
>             Fix For: dependencymanager-4.0.0
>
>
> 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) .



--
This message was sent by Atlassian JIRA
(v6.2#6252)