+1 I think some of the transports could be moved into own modules as well. - mqtt - zeroconf
And maybe the old kaha Or the dot generator; from the view package (wonder who uses it, or if its up to date) And the ftp blob suppor as well. For example you cant use file without having the ftp library on the classpath because they are in the same package. And I guess would be nice with spring xbean to be in own module as well. I guess I went a bit overboard with my "wish list" for AMQ core to be trimmed down. On Mon, Oct 1, 2012 at 4:18 PM, Hiram Chirino <[email protected]> wrote: > Considering how large the activemq-core module is, I was wondering if you > guys thought it might be beneficial to move the message stores into their > own modules. The leveldb store that is now integrated into the builds > gives us an example of how it can be done while still providing tight > integration /w XBean. The one down side I can think of is that users who > embed ActiveMQ would need to be aware of this change and update their > builds accordingly to avoid breaking. > > > -- > > ** > > *Hiram Chirino* > > *Engineering | Red Hat, Inc.* > > *[email protected] <[email protected]> | fusesource.com | redhat.com* > > *skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino> > * > > *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>* -- 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
