activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: [DISCUSS] OSGi support for Artemis
Date Fri, 13 Nov 2015 15:29:47 GMT

I’d much much rather see the split packages resolved than have an uber jar.

Can the packages be moved into a “common” jar or something that can be referenced by both?


Dan



> On Nov 13, 2015, at 10:27 AM, Clebert Suconic <clebert.suconic@gmail.com> wrote:
> 
> https://issues.apache.org/jira/browse/ARTEMIS-93
> 
> OSGI still an open task. Fancy contributing? (as the British would say)
> 
> The first thing thing I know we will need is an uber JAR. I think we
> talked about this during the last Apache Con with some folks.. and I
> also remember talking to some other folks.. that the first thing we
> will need is an Uber Jar...
> 
> 
> ActiveMQ has it being done here:
> 
> https://github.com/apache/activemq/tree/master/activemq-osgi
> 
> 
> Maybe that's an easy transfer?
> 
> 
> And that would take care of your issue of multiple split jars.. (We
> need the split jars as the clients don't want to have server
> objects... and other things that are best to be kept separate... you
> don't need the resource adapter on the client for instance).
> 
> 
> 
> On Fri, Nov 13, 2015 at 9:21 AM, Guillaume Nodet <gnodet@apache.org> wrote:
>> I was looking at supporting OSGi deployment for Artemis.
>> 
>> The first big problem I hit is the existence of split packages.  Split
>> packages are java packages shared across multiple jars (which become
>> bundles in OSGi).
>> Examples of those are org.apache.activemq.artemis.uri (shared between
>> artemis-jms-client and artemis-core-client) or
>> org.apache.activemq.artemis.api.config (shared between artemis-core-client
>> and artemis-commons).
>> The reason they are problematic is that in OSGi, each bundle has its own
>> class loader, importing classes from other packages based on packages.  The
>> same package can not be imported from 2 different bundles.
>> 
>> So the question is: would it be possible to get rid of those split packages
>> ? It can be done either by moving the classes from a jar to another one,
>> keeping the same package name, or by renaming one of the split package so
>> that there's no duplicate package names across jars.
>> 
>> Thoughts ?
>> Guillaume Nodet
> 
> 
> 
> -- 
> Clebert Suconic

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


Mime
View raw message