Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of heavy@ungoverned.org designates
 67.222.39.37 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=ungoverned.org;
	h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User;
	b=3eU0n0xh0dk5O5JjDAonTMOXpf8YwBU6YGHL+fWUOZ0zK/qsP0GkAqOkTVTmfV2WD+81YDlhXSDEILfAFjPM9zxZejEsUM46w6uK6NJeRYLbVbW+AkfmdZI8LGbuxNM8;
Message-ID: <499AF799.4000007@ungoverned.org>
Date: Tue, 17 Feb 2009 10:44:57 -0700
From: "Richard S. Hall" <heavy@ungoverned.org>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: dev@felix.apache.org
Subject: Re: Fragment bundle support
References: <499ABE18.3000404@BULL.NET>
In-Reply-To: <499ABE18.3000404@BULL.NET>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Could you try on trunk or the latest released snapshot?

There was a bug fixed recently, perhaps it is related:

    http://issues.apache.org/jira/browse/FELIX-852

-> richard

Fran�ois Fornaciari wrote:
> Hi,
>
> I know that the fragment bundle support is on going, but I would like 
> to submit a case that I have encountered.
>
> It seems that the installation order of a host bundle and its fragment 
> bundle modify the fragment support behaviour.
> I have made some tests and if the fragment bundle is installed before 
> the host bundle, everything goes fine. The host bundle can load a 
> class from its fragment and the classloader used to load the class 
> corresponds to the classloader of the host bundle. This case works 
> also fine when getting a resource.
>
> If I invert the installation order, that means if the host bundle is 
> installed before the fragment bundle, the host bundle fails to get the 
> same resource from the fragment. The class loading seems to work but 
> if try to print the used classloader, the host bundle loads the class 
> using the classloader of the fragment host.
>
> Is this behaviour expected?
>
> Regards,
> Fran�ois
>