geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet" <gno...@gmail.com>
Subject Re: Geronimo specs jars in OSGi
Date Thu, 17 Apr 2008 14:19:59 GMT
I've thought about this.  The main problem is that you end up having
two different
jars for the spec, one being a plain jar and another one being an OSGi bundle.
Both would not be compatible if the bundle embeds the spec jar, because non osgi
environment would not be able to load the jar inside the bundle.
Imho, creating two different jars would confuse the users and be more
error prone.

On Thu, Apr 17, 2008 at 4:10 PM, Alan D. Cabrera <list@toolazydogs.com> wrote:
>
>  On Apr 16, 2008, at 8:20 AM, Guillaume Nodet wrote:
>
>
>
> > In the past months, I've been working on making the specs jars from
> Geronimo working in an OSGi environment.
> > All these jars have been published and work great :-)
> > However, lots of these spec jars define factories (stax, saaj for example)
> that use the META-INF/services/ discovery mechanism to find an
> implementation of the spec and load it.  This mechanism does not fit well in
> OSGi (really, it does not), mainly because usually, the classloader
> containing the spec jar will not contain the implementation.
> > I'd like to work on these spec jars so that they will contain an OSGi
> BundleActivator that would change the behavior of these factories when
> deployed in an OSGi environment (without changing the behavior in other
> case).  The idea is that the activator would scan OSGi bundles when they are
> started to find META-INF/services and populate a map that would be used by
> the factory when creating an object before using the standard mechanism.
> >
> > The only real difference compared to what we currently have would be the
> addition of a package named org.apache.geronimo.specs.stax (for example)
> that would contain the needed classes (i suppose two classes), and the
> modification of the factories to delegate to one of these class before using
> the standard behavior (the class would do nothing if not deployed in an OSGi
> environment).
> > Has anyone any objection with such an enhancement in the specs jar ?
> >
>
>  I would prefer to have a virgin spec jar wrapped inside an OSGi bundle.
> Here the virgin factories would be overshadowed by the OSGi specific
> factories.
>
>  I feel strongly about this but am willing to discuss it.
>
>
>  Regards,
>  Alan
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Mime
View raw message