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

["Tuomas Kiviaho (JIRA)" <ji...@apache.org>]

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

Tuomas Kiviaho closed FELIX-4598.
---------------------------------

    Resolution: Fixed

Hello Pierre,

I'll close this since I doubt there will be another 3.x fix prior 4.0.0 although the fix would have been copy-pasting {{addedService/removedService}} methods both with five lines of code. From what I understood with a quick glance is that it indeed would not be a problem anymore in the new major release.

> 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) .



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