You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2015/03/17 10:43:38 UTC

[jira] [Resolved] (FELIX-4495) Candidates from already resolved fragments get ignored if no new hosts are available

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

Guillaume Nodet resolved FELIX-4495.
------------------------------------
    Resolution: Fixed

https://github.com/apache/felix/commit/d17068b666e8d3f7a6db49fa1db0386a2d8308bc

> Candidates from already resolved fragments get ignored if no new hosts are available
> ------------------------------------------------------------------------------------
>
>                 Key: FELIX-4495
>                 URL: https://issues.apache.org/jira/browse/FELIX-4495
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>    Affects Versions: resolver-1.0.0
>            Reporter: Thomas Watson
>            Assignee: Guillaume Nodet
>             Fix For: resolver-1.2.0
>
>         Attachments: org.apache.felix.resolver.patch
>
>
> org.apache.felix.resolver.Candidates.populateResource(ResolveContext, Resource) gets called for fragments even if they are already resolved so that we can attach them to more hosts as needed.
> The issue is that this method will throw a ResolutionException if the fragment cannot attach to any new hosts during the current resolve process.  This has the effect of removing any candidate capabilities provided by already resolved fragments.



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