felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Watson (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FELIX-4987) Dynamic package resolution with unresolvable or fragment package exports can lead to invalid wirings
Date Fri, 21 Aug 2015 15:05:46 GMT

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

Thomas Watson closed FELIX-4987.
--------------------------------

Thanks.  I merged the latest felix into my twatson/newResolver branch.  I'm still doing some
work to figure out the best settings to use for the executor for the framework's use of the
resolver.  You have any idea what the felix framework is going to do here?

> Dynamic package resolution with unresolvable or fragment package exports can lead to
invalid wirings
> ----------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-4987
>                 URL: https://issues.apache.org/jira/browse/FELIX-4987
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>         Environment: All
>            Reporter: Thomas Watson
>            Assignee: Guillaume Nodet
>             Fix For: resolver-1.6.0
>
>
> With the latest code in trunk calling org.apache.felix.resolver.ResolverImpl.resolve(ResolveContext,
Resource, Requirement, List<Capability>) with a List<Capability> containing a
Capability from a fragment will lead to an invalid Wire.
> This looks similar to FELIX-4897 and appears to be a regression.
> There are two types of failures.
> 1) Where the fragment has a valid host to resolve against.  In this case I would expect
the Wire.getProvider() to be the host revision for the fragment, but the current code returns
the fragment revision
> 2) Where the fragment has no valid host available.  In this case I would expect no Wire
to be returned in the result from the ResolverImpl.resolve call.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message