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/13 08:57:38 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14360076#comment-14360076 ]
Guillaume Nodet commented on FELIX-4495:
----------------------------------------
Proposed patch at
https://github.com/gnodet/felix/commit/da52e3b94c67060d19198506cd13f3480bc3bc31
> 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
> 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)