You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Tuomas Kiviaho <tu...@iki.fi> on 2008/02/08 12:28:22 UTC
Fine graining of activemq-core
Has there been any plans to fine grain activemq-core based on optional
dependencies.
-Separate library dedicated for a third party dependency would make it
possible to have activemq-core in parent classloader relative to for
instance activemq-spring.
-Removal of now obsolete dependencies from activemq-core pom.xml would
remove the need for explicit exclusions.
-No more NoClassDefFoundErrors caused by missing optional dependencies
This would ease out especially embedding which I found out to be quite a
trial-and-error iteration process on already existing system which uses same
dependencies as activemq-core. On the other hand overall complexity would be
increased.
--
View this message in context: http://www.nabble.com/Fine-graining-of-activemq-core-tp15353552s2354p15353552.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Fine graining of activemq-core
Posted by Guillaume Nodet <gn...@gmail.com>.
+1
On Fri, Feb 8, 2008 at 12:28 PM, Tuomas Kiviaho <tu...@iki.fi> wrote:
>
> Has there been any plans to fine grain activemq-core based on optional
> dependencies.
>
> -Separate library dedicated for a third party dependency would make it
> possible to have activemq-core in parent classloader relative to for
> instance activemq-spring.
> -Removal of now obsolete dependencies from activemq-core pom.xml would
> remove the need for explicit exclusions.
> -No more NoClassDefFoundErrors caused by missing optional dependencies
>
> This would ease out especially embedding which I found out to be quite a
> trial-and-error iteration process on already existing system which uses same
> dependencies as activemq-core. On the other hand overall complexity would be
> increased.
> --
> View this message in context: http://www.nabble.com/Fine-graining-of-activemq-core-tp15353552s2354p15353552.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Fine graining of activemq-core
Posted by Tuomas Kiviaho <tu...@iki.fi>.
Tuomas Kiviaho wrote:
>
> -No more NoClassDefFoundErrors caused by missing optional dependencies
>
And no more LinkageErrors. Today I had still one of those which are at least
easy to find because of the proper stack trace compared to the above.
--
View this message in context: http://www.nabble.com/Fine-graining-of-activemq-core-tp15353552s2354p15607035.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Fine graining of activemq-core
Posted by Guillaume Nodet <gn...@gmail.com>.
Here are some thoughts on what could be externalized:
* core (used by both the broker and client)
* broker
* client
* pool
* camel
* stores
* transports ..
I suppose we could keep backward compatibility by recreating an activemq-core
that would include all these modules.
On Thu, Feb 21, 2008 at 5:24 PM, Bruce Snyder <br...@gmail.com> wrote:
> On Fri, Feb 8, 2008 at 4:28 AM, Tuomas Kiviaho <tu...@iki.fi> wrote:
> >
> > Has there been any plans to fine grain activemq-core based on optional
> > dependencies.
> >
> > -Separate library dedicated for a third party dependency would make it
> > possible to have activemq-core in parent classloader relative to for
> > instance activemq-spring.
> > -Removal of now obsolete dependencies from activemq-core pom.xml would
> > remove the need for explicit exclusions.
> > -No more NoClassDefFoundErrors caused by missing optional dependencies
> >
> > This would ease out especially embedding which I found out to be quite a
> > trial-and-error iteration process on already existing system which uses same
> > dependencies as activemq-core. On the other hand overall complexity would be
> > increased.
>
> +1 I'd like to see the core slimmed down to only required items and
> push all the optional items out to the optional module.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
> Apache Geronimo - http://geronimo.apache.org/
>
> Blog: http://bruceblog.org/
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Fine graining of activemq-core
Posted by Bruce Snyder <br...@gmail.com>.
On Fri, Feb 8, 2008 at 4:28 AM, Tuomas Kiviaho <tu...@iki.fi> wrote:
>
> Has there been any plans to fine grain activemq-core based on optional
> dependencies.
>
> -Separate library dedicated for a third party dependency would make it
> possible to have activemq-core in parent classloader relative to for
> instance activemq-spring.
> -Removal of now obsolete dependencies from activemq-core pom.xml would
> remove the need for explicit exclusions.
> -No more NoClassDefFoundErrors caused by missing optional dependencies
>
> This would ease out especially embedding which I found out to be quite a
> trial-and-error iteration process on already existing system which uses same
> dependencies as activemq-core. On the other hand overall complexity would be
> increased.
+1 I'd like to see the core slimmed down to only required items and
push all the optional items out to the optional module.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/