the osgi support is a work in progress atm. An uber jar in karaf is the first step, the easiest thing to get working with automated tests.
We need to look at taking advantage of the new modules such that the deployment footprint in karaf can be reduced. Ie such that a simple jms client can just depend on activemq-client etc. On 15 January 2013 10:18, Claus Ibsen <[email protected]> wrote: > Hi > > So it seems that the various ActiveMQ components is now regular JAR > files, and there is a new uber OSGi bundle in activemq-osgi (4.5mb). > > So what's the store about that? > I can only assume OSGi pain with all the fine grained bundles, and > making an uber bundle fixes all that. > > It looks like the features.xml file hasn't been fully updated yet. > There seems to be a new activemq-broker and activemq-client, that > seems to be using the uber bundle. > > But some of the other features hasn't yet been updated, such as > activemq-spring. > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: [email protected] > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > -- http://redhat.com http://blog.garytully.com
