[
https://issues.apache.org/jira/browse/FELIX-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086165#comment-14086165
]
Pierre De Rop commented on FELIX-4598:
--------------------------------------
Hi Tuomas,
I have limited time since I'm travelling, going to vacations for two weeks,
however I would like to point out that since a couple of months we have
entirely revisited the dependency manager 4.0.0, using a new strong thread
model.
And I'm not sure but I believe that this problem from dm 3.2.0 (if it is really
a problem, I did not have time to really check) is probably not applicable in
DM 4.0.0.
Unfortunately, we have not yet commited the DM 4.0.0 version in
felix-trunk/dependencymanager, and you can take a look at the felix sandbox
here: [1]: it's a pure bndtools project, so you will have to install bndtools
before. But we will (hopefully) move this dm 4.0.0 soon to the felix-trunk.
then you can take a quick look at [2], which is a quick description about the
new architecture, and the BundleDependencyImpl is located in [3]
please close this issue if you think it's ok in DM 4.0.0. Thanks.
[1]
http://svn.apache.org/viewvc/felix/sandbox/pderop/dependencymanager-prototype/
[2]
http://svn.apache.org/viewvc/felix/sandbox/pderop/dependencymanager-prototype/org.apache.felix.dm/design.txt
[3]
http://svn.apache.org/viewvc/felix/sandbox/pderop/dependencymanager-prototype/org.apache.felix.dm/src/org/apache/felix/dm/impl/BundleDependencyImpl.java
PS: I will commit a fix as well as some test cases for your other issue
FELIX-4594, but this will be committed in the dm 4.0.0 (in the sandbox).
> 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)