geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: osgi >> trunk
Date Wed, 21 Oct 2009 19:15:00 GMT

On Oct 18, 2009, at 5:10 AM, Quintin Beukes wrote:

> What exactly will be the affect OSGi will have on Geronimo?

We don't know yet.  We hope it will make classloading simpler and  
generally make everything more flexible and interoperable.
> Will it simply replace the plugin architecture?

Hard to tell.  We might decide to just use blueprint, but I think that  
would really change or eliminate the deployers and make all the work  
they do happen each time you start the apps' bundles.  Right now we  
have more lifecycle states in plugins than are easily accessible in  
blueprint.  I want to get the server working before deciding what to  
do about this.

Felix/karaf has a "feature" idea which is kind of like our transitive  
dependency installation via geronimo-plugin.xml, but doesn't include  
the extracting of resources from bundles.  Maybe we can enhance their  
idea so we can use it.  Also,  AFAICT they don't have an idea of  
artifact-aliases.  Again, maybe they'd like our idea.

> And how will it, if at all, affect gbeans?

At the moment we are keeping gbeans pretty much the same as before,  
although there a a couple new special attributes, namely Bundle and  
BundleContext, that you can get injected automatically.  We definitely  
need more osgi integration in some way.  Two possibilities that I know  
of are:

-- keep gbeans, and provide a way to expose them as osgi services via  
an annotation and/or GBeanInfo flag.
-- drop gbeans and move everything over to blueprint.

I don't think I know enough about osgi and blueprint to say what  
direction we should go in yet.

david jencks

> Quintin Beukes
> On Sat, Oct 17, 2009 at 7:02 PM, David Jencks  
> <> wrote:
>> On Oct 17, 2009, at 5:04 AM, Quintin Beukes wrote:
>>> Is it tricky to build? I would like to take a look at what you guys
>>> have achieved so far :>
>> It's beyond tricky, only the framework builds so far.  For that,  
>> you need to
>> build some servicemix bundles locally.  I'll try to publish the  
>> servicemix
>> bundles in the next few days.  There have been a few posts recently  
>> about
>> how to get the framework to build, I would consult them for  
>> additional
>> hints.
>> I'm trying to get plugins/j2ee to build: at that point it should be  
>> possible
>> for lots of people to work more or less independently in parallel  
>> on fixing
>> the other plugins.
>> thanks
>> david jencks
>>> Quintin Beukes
>>> On Fri, Oct 16, 2009 at 10:41 PM, David Jencks < 
>>> >
>>> wrote:
>>>> Thanks Donald,
>>>> I opened GERONIMO-4916 to track this, removed the old framework,  
>>>> and
>>>> moved
>>>> over the osgi framework from sandbox.
>>>> Now we just have to get it all to work :-)
>>>> thanks
>>>> david jencks
>>>> On Oct 16, 2009, at 12:30 PM, Donald Woods wrote:
>>>>> Branch of current pre-OSGi trunk has been created at -
>>>>> Let the OSGi merge begin....
>>>>> -Donald
>>>>> David Jencks wrote:
>>>>>> I have the sandbox osgi framework working enough to start the  
>>>>>> geronimo
>>>>>> plugins, so I'm planning to move this work into trunk so we can 

>>>>>> all
>>>>>> pitch in
>>>>>> more easily on getting the rest of geronimo running on osgi.
>>>>>> There's one legal issue to take care of first, since I copied  
>>>>>> in some
>>>>>> plexus code that is not clearly available under asl2.  The code 

>>>>>> appears
>>>>>> to
>>>>>> have been derived from ant, so I'm going to see if we can get  
>>>>>> the same
>>>>>> results by importing or using ant code.
>>>>>> I think that Donald is planning to make a branch off of trunk  
>>>>>> for a
>>>>>> convenient place to try out jpa2 stuff at least until we have the
>>>>>> equivalent
>>>>>> working under osgi.
>>>>>> If you have any concerns about this please speak up!
>>>>>> thanks
>>>>>> david jencks

View raw message