[rabbitmq-discuss] Rabbit-Spring integration

Sebastien PLISSON splisson at veodia.com
Thu Feb 21 21:41:35 GMT 2008


I agree with you David, I'd prefer not use JMS but have Spring-amqp classes.

Regards,
Sebastien


On 2/21/08 1:36 PM, "Alexis Richardson" <alexis.richardson at cohesiveft.com>
wrote:

> David
> 
> Your first intuition is correct.  This would be much better than the
> second option, in the long run.  We would love to work with folks on
> this.
> 
> alexis
> 
> 
> On Thu, Feb 21, 2008 at 9:29 PM, David Peterson <peterson at orbitec.com.au>
> wrote:
>> 
>>  Hi All,
>> 
>>  Thanks Alexis, Sebastian. I'm thinking the best way would be to create a
>>  com.rabbitmq.client.spring (or "org.springframework.amqp") set of base
>>  classes that parallel the org.springframework.jms classes and implement
>>  a similar kind of MessageListener and MessageListenerContainer callback
>>  model.
>> 
>>  If it's not JMS, then the AMQP Rabbit stuff should not extend /
>>  implement JMS interfaces. Rather we should create our own parallel
>>  heirarchy. Thoughts / comments please?
>> 
>>  Regs,
>> 
>>  Dave
>> 
>> 
>> 
>> 
>>  On Thu, 2008-02-21 at 08:09 -0800, Sebastien PLISSON wrote:
>>> I attached a sample spring configuration.
>>> 
>>> Sebastien
>>> 
>>> 
>>> On 2/21/08 7:48 AM, "Alexis Richardson" <alexis.richardson at cohesiveft.com>
>>> wrote:
>>> 
>>>> Hi Sebastien
>>>> 
>>>> On Thu, Feb 21, 2008 at 3:45 PM, Sebastien PLISSON <splisson at veodia.com>
>>>> wrote:
>>>>> Hi,
>>>>> 
>>>>>  I started integrating the communication with RabbitMQ server using Spring
>>>>>  2.5. I use the Qpid M1 java client to do that because it provides the JMS
>>>>>  Interface usable by the Spring JMS classes.
>>>>>  This configuration allows the usage of MessageListenerAdapter,
>>>>>  MessageListenerContainer, JmsGateway, ...
>>>> 
>>>> Thanks for that :-)
>>>> 
>>>> Could you show us any of your client classes or config files?
>>>> 
>>>> 
>>>>>  I hope that one day we will have a full amqp spring template... ;-)
>>>> 
>>>> David, over to you!
>>>> 
>>>> alexis
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>>  wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> Hi David
>>>>>> 
>>>>>> On Thu, Feb 21, 2008 at 1:09 AM, David Peterson <peterson at orbitec.com.au>
>>>>>> wrote:
>>>>>>> 
>>>>>>>  We're currently evaluating RabbitMQ in a Java environment as an
>>>>>>>  alternative to a conventional JMS messaging system.
>>>>>> 
>>>>>> Excellent :-)
>>>>>> 
>>>>>> Do you have any non-Java cases too?  Or are you currently thinking of
>>>>>> a Java2Java messaging set-up?
>>>>>> 
>>>>>> [ I ask because we've just released a .NET client, which will interop
>>>>>> with Java over AMQP, plus of course the STOMP and HTTP clients seem
>>>>>> useful to Java users. ]
>>>>>> 
>>>>>> 
>>>>>>>  Ideally, I would
>>>>>>>  like to "plug-in" rabbit in a manner similar to the way that JMS is
>>>>>>>  supported by Spring 2.x (i.e. a MessageContainer and MessageListener
>>>>>>>  implementation that allows "message-driven POJOs").
>>>>>> 
>>>>>> This is eminently sensible.
>>>>>> 
>>>>>> 
>>>>>>>  My question is: are there any spring support classes for Rabbit at this
>>>>>>>  time that provide this kind of integration?
>>>>>> 
>>>>>> Not yet.. We did look at it, and it seems like a refactoring of the
>>>>>> Spring messaging classes using RabbitMQ's Java client, would be
>>>>>> straightforward.
>>>>>> 
>>>>>> 
>>>>>>>  I've already started prototyping a few ideas in this regard and I'm
>>>>>>>  wondering whether they would be welcome within the Java client, perhaps
>>>>>>>  within a a com.rabbitmq.spring.* package heirarchy?
>>>>>> 
>>>>>> That would be extremely welcome!
>>>>>> 
>>>>>> I am cc'ing some potentially interested parties.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>>  A second question: I note that Rabbit defines the various AMQP
>>>>>>>  interfaces inside the com.rabbitmq.* heirarchy. Do you know whether
>>>>>>>  there are any plans by the AMQP consortium to split this out into an
>>>>>>>  "org.amqp.*" heirarchy that could be implemented against by any Java
>>>>>>> API
>>>>>>>  (rabbit included)?
>>>>>> 
>>>>>> Yes.  The AMQP Working Group believes that a client API could be
>>>>>> useful, for example a set of Java interface classes in a package
>>>>>> org.amqp.*
>>>>>> 
>>>>>> What do you think of the RabbitMQ Java and C# APIs?
>>>>>> 
>>>>>> 
>>>>>>>  Thanks in advance for your help and guidance.
>>>>>> 
>>>>>> It's a pleasure.
>>>>>> 
>>>>>> alexis
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>  _______________________________________________
>>>>>>>  rabbitmq-discuss mailing list
>>>>>>>  rabbitmq-discuss at lists.rabbitmq.com
>>>>>>>  http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>  --
>>  Orbitec Pty Ltd
>>  Suite 1-11, 460 Pacific Hwy
>>  St. Leonards NSW 2065
>>  AUSTRALIA
>> 
>>  Phone:  +61 (0)2 8002 4780
>>  Mobile: +61 (0)415 943 940
>>  Email:  support at orbitec.com.au
>>  Web:    http://www.orbitec.com.au
>> 
>>  This email may contain CONFIDENTIAL information intended solely for
>>  the use of the intended recipient. If you receive this email in error,
>>  we ask that you notify us by email of our error and then delete the
>>  email as soon as possible. We ask that you do not copy, store or
>>  distribute any message that you have received in error and we thank you
>>  for your assistance.
>> 
>> 
>> 
> 
> 





More information about the rabbitmq-discuss mailing list