felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-2858) [Framework] Modify resolver to be self-contained with respect to fragment handling
Date Mon, 07 Mar 2011 20:09:59 GMT

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

Richard S. Hall commented on FELIX-2858:

Funny, it compiles for me. However, that import should not be in there, so I removed it. It
should work now.

> [Framework] Modify resolver to be self-contained with respect to fragment handling
> ----------------------------------------------------------------------------------
>                 Key: FELIX-2858
>                 URL: https://issues.apache.org/jira/browse/FELIX-2858
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: framework-3.0.9
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: framework-3.2.0
> Currently, the resolver does not handle fragments or even know about them at all. The
resolver state, which is an external entity handles this. This approach limits reuse of the
resolver since it is not self-contained. The resolver should be modified so that it directly
processes fragments. To do this, it will have to create wrapped modules to synthesize hosts
with attached fragments. This is similar to what currently happens in the resolver state.
The main difference is that the resolver state does this at bundle install time, which is
more efficient. A self-contained resolver will have to do it every time there is a resolve
involving fragments, so it might be less efficient.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message