Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gaurav.cs.sharma@gmail.com
 designates 209.85.210.43 as permitted sender)
Subject: Re: Move message stores into separate modules?
References: 
 <CAGZ-RDLtB-4qfTixECwHV9KJE0QdwOXo7V7eULKFJ=prM3DMZA@mail.gmail.com>
 <CAGB5yNnHDbaaaG8aJyXYS-aQn7c6AcfYEV_UwDKGF2sGWPN5gg@mail.gmail.com>
 <CAGZ-RDJkK14cGaVktBhqVv4gC7HpM-iR0vpDusH3j6gyk3JDgQ@mail.gmail.com>
 <CAGeh-pH-nRmKmxopkbyFbg+v-5j8z53Y5Op1S3XYdLOLPFGnag@mail.gmail.com>
 <CAGZ-RD+dWx-g21kvoyLYvkZK09R5f5kMeHmgMaWJ_Q2JHPJhGw@mail.gmail.com>
From: Gaurav Sharma <gaurav.cs.sharma@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: 
 <CAGZ-RD+dWx-g21kvoyLYvkZK09R5f5kMeHmgMaWJ_Q2JHPJhGw@mail.gmail.com>
Message-Id: <ACF5FC48-D888-4ADB-9A04-230F7526AF5C@gmail.com>
Date: Mon, 1 Oct 2012 09:02:09 -0700
To: "dev@activemq.apache.org" <dev@activemq.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

+1 for the split, will also improve testability and generally easy-on for ne=
w contributors

On Oct 1, 2012, at 8:13, Hiram Chirino <hiram@hiramchirino.com> wrote:

> Yeah.  That's what I figure.  I'm sure we can figure out a way to decouple=

> the two and still be able to embed broker if the broker jar is present.
>=20
> BTW: Having a separate client jar will also make it simpler to ship a JMS
> client implementation with Apollo.  Hell, if the way the broker is
> 'embedded' is pluggable enough, perhaps we can get the JMS client to boot
> Apollo as the embedded broker.
>=20
> On Mon, Oct 1, 2012 at 11:06 AM, Dejan Bosanac <dejan@nighttale.net> wrote=
:
>=20
>> The problem with activemq-client is that we usually need to support
>> embedded broker and that means all transports, stores and stuff. But
>> that doesn't mean we can't create activemq-client, that only supports
>> tcp transport which I guess 90% of folks use on the client side.
>>=20
>>=20
>> Regards
>> --
>> Dejan Bosanac
>> ----------------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> dbosanac@redhat.com
>> Twitter: @dejanb
>> Blog: http://sensatic.net
>> ActiveMQ in Action: http://www.manning.com/snyder/
>>=20
>>=20
>> On Mon, Oct 1, 2012 at 4:45 PM, Hiram Chirino <hiram@hiramchirino.com>
>> wrote:
>>> On Mon, Oct 1, 2012 at 10:38 AM, Claus Ibsen <claus.ibsen@gmail.com>
>> wrote:
>>>=20
>>>> +1
>>>>=20
>>>> I think some of the transports could be moved into own modules as well.=

>>>> - mqtt
>>>> - zeroconf
>>>>=20
>>>> 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=
.
>>>>=20
>>>> I guess I went a bit overboard with my "wish list" for AMQ core to be
>>>> trimmed down.
>>> totally aggree... and hell if we are going to be talking about wish
>> lists,
>>> here's one that sounds a little crazy:  split activemq-core into a
>>> activemq-client and activemq-broker module.  But we probably need to
>> first
>>> trim down all the fat before we can tackle that :)
>>>=20
>>>=20
>>>=20
>>>>=20
>>>>=20
>>>> On Mon, Oct 1, 2012 at 4:18 PM, Hiram Chirino <hiram@hiramchirino.com>
>>>> 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.
>>>>>=20
>>>>>=20
>>>>> --
>>>>>=20
>>>>> **
>>>>>=20
>>>>> *Hiram Chirino*
>>>>>=20
>>>>> *Engineering | Red Hat, Inc.*
>>>>>=20
>>>>> *hchirino@redhat.com <hchirino@redhat.com> | fusesource.com |
>> redhat.com
>>>> *
>>>>>=20
>>>>> *skype: hiramchirino | twitter: @hiramchirino<
>>>> http://twitter.com/hiramchirino>
>>>>> *
>>>>>=20
>>>>> *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
>>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> Red Hat, Inc.
>>>> FuseSource is now part of Red Hat
>>>> Email: cibsen@redhat.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus
>>>> Blog: http://davsclaus.com
>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>=20
>>>=20
>>>=20
>>> --
>>>=20
>>> **
>>>=20
>>> *Hiram Chirino*
>>>=20
>>> *Engineering | Red Hat, Inc.*
>>>=20
>>> *hchirino@redhat.com <hchirino@redhat.com> | fusesource.com | redhat.com=

>> *
>>>=20
>>> *skype: hiramchirino | twitter: @hiramchirino<
>> http://twitter.com/hiramchirino>
>>> *
>>>=20
>>> *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
>=20
>=20
>=20
> --=20
>=20
> **
>=20
> *Hiram Chirino*
>=20
> *Engineering | Red Hat, Inc.*
>=20
> *hchirino@redhat.com <hchirino@redhat.com> | fusesource.com | redhat.com*
>=20
> *skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchir=
ino>
> *
>=20
> *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*