aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <>
Subject [jira] [Resolved] (ARIES-1446) ResolveContext should stop searching for capabilities once it found a match
Date Thu, 04 Feb 2016 19:01:39 GMT


John Ross resolved ARIES-1446.
    Resolution: Not A Problem
      Assignee: John Ross

For dependencies, section 134.6 states:

"This resolve context must search Repositories in the following order when searching for capabilities
to satisfy content dependencies within the ResolveContext.findProviders method. The Content
Repository, Preferred Provider Repository, System Repository and Local Repository must all
be searched and all the results presented to the Resolver with a corresponding preference.
If a result was found in these repositories, searching the registered Repository services
is optional, but if no result was found yet, the registered Repository services must be searched.
The order of matching capabilities presented to the Resolver must coincide with the Repository
search order."

It goes on to list the search order: (1) content, (2) preferred provider, (3) system, (4)
local, and (5) repository services. The last is optional if at least one matching capability
was found in any of the previous four. An implementation must always search the first four
and order the capabilities accordingly.

I imagine you're thinking about content resources which are different. As described in section, an implementation must search repositories in the prescribed order and stop as
soon as any matching resources are found. In Aries, this is all handled by SubsystemResource.findContent(Requirement).
The resolve context is not used.

> ResolveContext should stop searching for capabilities once it found a match
> ---------------------------------------------------------------------------
>                 Key: ARIES-1446
>                 URL:
>             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

View raw message