You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Thomas Watson (JIRA)" <ji...@apache.org> on 2015/08/03 21:36:04 UTC
[jira] [Updated] (FELIX-4987) Dynamic package resolution with
unresolvable or fragment package exports can lead to invalid wirings
[ https://issues.apache.org/jira/browse/FELIX-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Watson updated FELIX-4987:
---------------------------------
Summary: Dynamic package resolution with unresolvable or fragment package exports can lead to invalid wirings (was: Dynamic package resolution with fragment package exports can lead to invalid wirings)
> 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
>
> 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)