Message Driven POJOs with Spring

Spring 2.0 introduced support for Message-Driven POJOs meaning that it is now possible to receive JMS messages asynchronously and delegate the handling of those messages to simple objects even within a lightweight application running outside of any application server. If your POJO has a return value, it will automatically be sent to a response destination.

After a quick overview of Spring's JMS support, we will build a Message-Driven POJO sample application from the ground up. This will include sending a Message as a request and receiving a reply across separate JVMs. You will learn how to configure the Message-Driven POJO without writing a single line of messaging code. You will also learn how to configure the pool of concurrent consumers and integrate with Spring's transaction management. We will use the JMS namespace available as of Spring 2.5, and we will even explore the possibility of delegating to a Groovy-scripted object.

About Mark Fisher

Mark Fisher is an engineer at Pivotal and has been a member of the Spring team for over 7 years. Currently he co-leads Spring XD and also manages the group responsible for Spring Integration, Spring Batch, and Spring AMQP. Mark has provided consulting services for dozens of clients and has trained hundreds of developers how to use the Spring Framework and related projects effectively. He speaks regularly at conferences and user groups in America and Europe and is one of the authors of Spring Integration in Action, published by Manning in 2012.

More About Mark »