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

["Thomas Watson (JIRA)" <ji...@apache.org>]

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

Thomas Watson updated FELIX-4495:
---------------------------------

    Attachment: org.apache.felix.resolver.patch

Fixed by checking that the resource is a fragment and already resolved before failing populateResource for a fragment.

> 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
>            Reporter: Thomas Watson
>         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.2#6252)