[rabbitmq-discuss] status of available message buses compatible with Java client

Tue Jun 29 18:07:58 BST 2010

Hi,

We are moving to git today/tomorrow.  There will be some changes in terms of moving some admin functionality around the maven modules and internal structuring of the erlang mappings to rabbit function.  

We are also going to shift to a simplistic resource model for M1 instead of caching channels as we need more time to get the resource management correct.  The issue is that we really need to cache connection/channels pairs since an error on a single channel ends up effecting the whole connection - this means all async consumers are effected and stop processing based on the behavior of one consumer.  

Yea, July 9th is still our target date, no docs yet and we need more integration testing as well :)

Mark

> -----Original Message-----
> From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-
> discuss-bounces at lists.rabbitmq.com] On Behalf Of Shane
> Sent: Tuesday, June 29, 2010 12:24 PM
> To: rabbitmq-discuss at lists.rabbitmq.com
> Subject: Re: [rabbitmq-discuss] status of available message buses
> compatible with Java client
> 
> Hi Mark,
> 
> I appreciate your replies. You've helped to solidify some of my design
> decisions including using your unreleased spring-amqp project. I've
> noticed that there hasn't been any commits to the subversion repo you
> pointed me to. Have you already moved to git? I also noticed the
> documentation is not there yet and I assume you are working on that
> now. I know you mentioned a July 9th date for an initial release but
> I'd be interested in any other changes before then if that's cool?
> 
> Thanks again
> 
> On Jun 24, 4:44 pm, Mark Pollack <mpoll... at vmware.com> wrote:
> > Hi,
> >
> > Was not planning on it for M1.  We need to see what the impact is on
> the underlying APIs, but it will certainly be a roadmap item if not
> addressed in M1.
> >
> > Mark
> >
> > (yes - another Mark working on the same thing at SpringSource :)
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: rabbitmq-discuss-boun... at lists.rabbitmq.com [mailto:rabbitmq-
> > > discuss-boun... at lists.rabbitmq.com] On Behalf Of Shane
> > > Sent: Thursday, June 24, 2010 4:33 PM
> > > To: rabbitmq-disc... at lists.rabbitmq.com
> > > Subject: Re: [rabbitmq-discuss] status of available message buses
> > > compatible with Java client
> >
> > > Awesome. I noticed that the code isn't currently compatible with
> > > version 1.8 of the java client. Are you planning on supporting 1.8
> in
> > > the short term?
> >
> > > On Jun 24, 11:30 am, Mark Fisher <markfis... at vmware.com> wrote:
> > > > Shane,
> >
> > > > We are planning to release the first milestone (1.0.0.M1) on
> Friday
> > > July 9th.
> >
> > > > -Mark
> > > > ________________________________________
> > > > From: rabbitmq-discuss-boun... at lists.rabbitmq.com [rabbitmq-
> discuss-
> > > boun... at lists.rabbitmq.com] On Behalf Of Shane
> > > [sh... at digitalsanctum.com]
> > > > Sent: Thursday, June 24, 2010 10:40 AM
> > > > To: rabbitmq-disc... at lists.rabbitmq.com
> > > > Subject: Re: [rabbitmq-discuss] status of available message buses
> > > compatible    with Java client
> >
> > > > Mark,
> >
> > > > I've started looking at the code it's looking good. Any estimate
> on
> > > > when an initial public version will be available?
> >
> > > > Shane
> >
> > > > On Jun 23, 8:09 pm, Mark Fisher <markfis... at vmware.com> wrote:
> >
> > > > > Shane, see my replies inline...
> >
> > > > > On Jun 23, 2010, at 6:28 PM, Shane wrote:
> >
> > > > > > I'm still feeling my way around RabbitMQ (as you might have
> > > noticed
> > > > > > from the number of posts I've written lately). One decision
> I'm
> > > > > > wrestling with is what to use for message routing with the
> Java
> > > > > > client. I've started looking into the following:
> >
> > > > > > - Writing my own helper classes with Spring
> > > > > > - Apache Camel
> > > > > > - Spring Integration with OpenCredo's contributions (amq
> > > template, amq
> > > > > > spring integration)
> >
> > > > > We will soon be releasing the first milestone of our Spring
> AMQP
> > > project. That includes support at the same basic level as Spring's
> JMS
> > > support (AmqpTemplate, SimpleMessageListenerContainers for Message-
> > > driven POJOs, MessageConverter strategies, and more). We will be
> > > providing Spring Integration Channel Adapters, Gateways, etc. that
> will
> > > build on top of that functionality.
> >
> > > > > > Since RabbitMQ was recently acquired by SpringSource, SI
> > > w/OpenCredo
> > > > > > seems like the natural choice but there hasn't been any
> > > development on
> > > > > > the OpenCredo stuff since March? (looking at github).
> >
> > > > > We're going to be collaborating with OpenCredo on the project I
> > > mentioned above, and that project is actually quite active already.
> > > However, as I mentioned, we're just now approaching the first
> milestone
> > > release. We'll be moving to Git any moment now, but until it's
> moved,
> > > you can browse the current codebase
> > > here:https://src.springsource.org/svn/se-amqp/trunk/(afterthemove
> it
> > > will be at git.springsource.org/spring-amqp)
> >
> > > > > > Although Apache Camel seems to be more mature, I'd rather go
> the
> > > > > > Spring Integration route since all of our apps already use
> Spring
> > > for
> > > > > > dependency injection, etc.
> >
> > > > > As the lead of Spring Integration, I'm a bit biased. That said,
> if
> > > your main concern is having a solid (and "mature" I might add)
> Spring
> > > foundation with implementations that are absolutely consistent with
> > > Spring, then Spring Integration is probably the best choice (and
> 2.0 GA
> > > is only a couple months away).
> >
> > > > > > Can someone from Rabbit comment on the state of development
> with
> > > > > > respect to integration with Spring? Is the contributions from
> > > > > > OpenCredo going to be used?
> >
> > > > > Hopefully this question has been answered above. Let me know if
> > > there is anything that I missed.
> >
> > > > > Regards,
> > > > > Mark
> >
> > > > > > I'm also interested in other message bus solutions people are
> > > using
> > > > > > with the Java client.
> >
> > > > > > Thanks again,
> > > > > > Shane
> > > > > > _______________________________________________
> > > > > > rabbitmq-discuss mailing list
> > > > > > rabbitmq-disc... at lists.rabbitmq.com
> > > > > >http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-
> > > discuss
> >
> > > > > _______________________________________________
> > > > > rabbitmq-discuss mailing list
> > > > > rabbitmq-
> disc... at lists.rabbitmq.comhttp://lists.rabbitmq.com/cgi-
> > > bin/mailman/listinfo/rabbitmq-discuss
> >
> > > > _______________________________________________
> > > > rabbitmq-discuss mailing list
> > > > rabbitmq-disc... at lists.rabbitmq.comhttp://lists.rabbitmq.com/cgi-
> > > bin/mailman/listinfo/rabbitmq-discuss
> > > > _______________________________________________
> > > > rabbitmq-discuss mailing list
> > > > rabbitmq-
> disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-
> > > bin/mailman/listinfo/rabbitmq-discuss
> > > _______________________________________________
> > > rabbitmq-discuss mailing list
> > > rabbitmq-disc... at lists.rabbitmq.com
> > >https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> >
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-
> bin/mailman/listinfo/rabbitmq-discuss
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss