Comments on: Message Driven POGOs: When Groovy, Spring and OpenMQ collide http://blogs.bytecode.com.au/glen/2008/08/14/message-driven-pogos-when-groovy-spring-and-openmq-collide.html Java, XML and all that Jazz... from Canberra, Australia Mon, 20 May 2013 08:15:07 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Glen Smith http://blogs.bytecode.com.au/glen/2008/08/14/message-driven-pogos-when-groovy-spring-and-openmq-collide.html#comment-775 Glen Smith Mon, 25 Aug 2008 19:23:54 +0000 http://blogs.bytecode.com.au/glens/2008/08/14/message-driven-pogos-when-groovy-spring-and-openmq-collide/#comment-775 Thanks for the link, Joe. Great idea. That’s even tighter code!

]]> By: Joe Rinehart http://blogs.bytecode.com.au/glen/2008/08/14/message-driven-pogos-when-groovy-spring-and-openmq-collide.html#comment-774 Joe Rinehart Mon, 25 Aug 2008 13:40:45 +0000 http://blogs.bytecode.com.au/glens/2008/08/14/message-driven-pogos-when-groovy-spring-and-openmq-collide/#comment-774 Hey Glen,

I just got into Spring + JMS + Groovy last week, and found that you can even go a little further with maintaining the “POGO”-ness of your ThumbnailListener. By using Spring 2.0′s MessageListenerAdapter, you can remove the need to implement MessageListener and onMessage, letting the listener be used seamlessly by other another bean or JMS.

Details there:

http://blog.springsource.com/main/2006/08/11/message-driven-pojos/

Cheers,

Joe

]]> By: Dan Oxlade http://blogs.bytecode.com.au/glen/2008/08/14/message-driven-pogos-when-groovy-spring-and-openmq-collide.html#comment-773 Dan Oxlade Sun, 17 Aug 2008 21:24:49 +0000 http://blogs.bytecode.com.au/glens/2008/08/14/message-driven-pogos-when-groovy-spring-and-openmq-collide/#comment-773 If you use the spring jms schema you can reduce the amount of code, the container bean definition becomes simpler and your listener wouldn’t need to implement MessageListener and the method signiture could just be onMessage(Map message)

]]>