[
https://issues.apache.org/jira/browse/ARIES-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134008#comment-15134008
]
Bas commented on ARIES-1446:
----------------------------
I found it, your quote is from the version 6 spec. I read the version 5 spec.
The way this should work changed between specs. So I guess spec. 6 is the one
to follow?
Qoute from version 5 spec:
In order to use the Resolver service the Subsystems implementation has to
provide a ResolveContext
object that represents the currently installed Subsystems and their constituent
resources. This
resolve context must search Repositories in the following order when searching
for capabilities to
satisfy content dependencies the ResolveContext.findProviders method:
1 The Content Repository. If matching capabilities are found in the Subsystem's
Content Repository
then they must be used to satisfy content resource requirements and no other
Repositories are
searched. If no matching capabilities are found then continue to the next step.
2 The Preferred Repository for the Subsystem. If matching capabilities are
found in the Subsystem's
Preferred Repository then they are used to satisfy content resource
requirements and no other
Repositories are searched. If no matching capability is found then continue to
the next step.
...
...
...
...
> ResolveContext should stop searching for capabilities once it found a match
> ---------------------------------------------------------------------------
>
> Key: ARIES-1446
> URL: https://issues.apache.org/jira/browse/ARIES-1446
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Affects Versions: subsystem-2.0.6, subsystem-2.0.8
> Reporter: Bas
> Assignee: John Ross
> Labels: subsystem
>
> If I read the osgi.enterprise-5.0.0 spec correctly it says in section 134.6
> that searching for capabilities should stop once a repository returns
> results. The current resolvecontext does not do this but instead keeps on
> searching which might return results.
> Don't know if this causes behaviour that is not according to spec. but I can
> imagine that it might cause the resolver to have a more difficult time or it
> resolves to something that it should not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
