felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4914) Resolution problem with fragments
Date Mon, 08 Jun 2015 07:03:01 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576676#comment-14576676
] 

Guillaume Nodet commented on FELIX-4914:
----------------------------------------

Actually, the problem comes from the fact that the WrappedResource does not include identities
from fragments.
In my model, I use a dummy resource as the only mandatory resource and add to that one several
requirements, usually identity requirements.
However, the WrappedResource explicitly filter out identity capabilities, so this leads to
those use constraints conflicts.

I pushed a possible fix in a private branch at
  https://github.com/gnodet/felix/commits/FELIX-4914

The idea is to add the fragments identity capabilities to the wrapped host as done for all
other capabilities, then make sure the wire is correctly created to the actual fragment.

If there's no objections, I'll commit the fix to trunk.
[~rickhall] [~tjwatson] Thoughts ?


> Resolution problem with fragments
> ---------------------------------
>
>                 Key: FELIX-4914
>                 URL: https://issues.apache.org/jira/browse/FELIX-4914
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: framework-5.0.0, resolver-1.2.0
>            Reporter: Guillaume Nodet
>
> When a fragment has a requirement that can be fulfilled by another fragment, there are
chances that the resolution fail, depending on the order in which fragments are considered.
 The {{Candidates#prepare}} method is not complete, and in some cases, can leave non-wrapped
capabilities in the candidates map, possibly leading to usage constraints problems.
> I have a test case which I'm trying to clean a bit.



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

Mime
View raw message