Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of heavy@ungoverned.org
 designates 69.89.24.10 as permitted sender)
Message-ID: <475575BE.4090306@ungoverned.org>
Date: Tue, 04 Dec 2007 10:43:58 -0500
From: "Richard S. Hall" <heavy@ungoverned.org>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: dev@felix.apache.org
Subject: Re: [FELIX] OBR resolving system packages and the Execution
 Environment
References: 
 <F1886AFB628EA94098943970F1563B89F84032@LINUS.proteus-technologies.com>
 <475476D4.3070902@ungoverned.org>
 <F1886AFB628EA94098943970F1563B89F840AB@LINUS.proteus-technologies.com>
 <F1886AFB628EA94098943970F1563B89F840AD@LINUS.proteus-technologies.com>
In-Reply-To: 
 <F1886AFB628EA94098943970F1563B89F840AD@LINUS.proteus-technologies.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Roshan A. Punnoose wrote:
> I'm not sure if it is just my implementation, but when I added a
> repository xml that required a System Package (one that is already
> available in java "org.xml.sax") or a ExecutionEnvironment requirement
> ("ee") the resolve does not work. Is there any current workaround?
>   

OBR does deal with EE yet, but it should work with packages available 
from System Bundle, I believe.

-> richard
> Roshan
>
> -----Original Message-----
> From: Roshan A. Punnoose [mailto:rpunnoose@proteus-technologies.com] 
> Sent: Tuesday, December 04, 2007 8:31 AM
> To: dev@felix.apache.org
> Subject: RE: [FELIX] OBR tied to the BundleContext
>
> Actually I found my issue. What happened is the LocalResource in the
> ResolverImpl does find all bundles associated in the current
> BundleContext and will update with the latest stream if an update is
> required. However, my bundle that I wanted to update had a
> symbolicName=temp;singleton=true, and the repository xml did not have
> the "singleton" property. So the ResolverImpl did not recognize that I
> had a "temp" bundle already installed and only required an update. What
> should happen I believe is that the LocalResourceImpl should parse the
> symbolicName to "temp" and not "temp;singleton=true". 
>
> Roshan
>
> -----Original Message-----
> From: Richard S. Hall [mailto:heavy@ungoverned.org] 
> Sent: Monday, December 03, 2007 4:36 PM
> To: dev@felix.apache.org
> Subject: Re: [FELIX] OBR tied to the BundleContext
>
> Roshan,
>
> I am not sure I understand the situation you are describing.
>
> Adding a repository XML to repo admin will not be impacted by what 
> bundles are currently installed in the framework. OBR just maintains a 
> list of available bundles. If you try to install a bundle from a 
> repository, OBR's resolve process will look at what is installed locally
>
> to make decisions about what it needs to download.
>
> If a bundle is already installed, it should not download it again, 
> unless it determines that it needs a different version or something.
>
> -> richard
>
> Roshan A. Punnoose wrote:
>   
>> Hi,
>>
>>  
>>
>> Looking into the OBR code, I think it might be useful to have the OBR
>> RepositoryAdmin tied to the BundleContext and the bundles that are
>> already active in OSGi container. Right now, I am running the felix
>>     
> OBR
>   
>> bundle in Equinox, but it does not tie to the BundleContext. So when I
>> try and add an OBR repository xml containing plugins that already
>>     
> exist
>   
>> in the container, it throws an exception because these bundles already
>> exist in the container. However, if the OBR bundle was tied to the
>> BundleContext, it should see that there are already Resources/Bundles
>> available to the container and not try and deploy these.
>>
>>  
>>
>> I can see where to do it in the code, and I can submit a patch for it.
>> Is this a path that seems reasonable to you?
>>
>>  
>>
>> Roshan
>>
>>
>>   
>>