Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Mon, 28 Mar 2011 15:30:07 +0000 (UTC)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: 
 <1294605621.16878.1301326207034.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <696350047.11787.1298493398408.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (FELIX-2858) [Framework] Modify resolver to be
 self-contained with respect to fragment handling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Richard S. Hall closed FELIX-2858.
----------------------------------

    Resolution: Fixed

Fragment handling now handled by the resolver.

> [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