From the course: Spring: Messaging with JMS

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

JMS 1.1 versus Spring JMS API

JMS 1.1 versus Spring JMS API - Spring Tutorial

From the course: Spring: Messaging with JMS

Start my 1-month free trial

JMS 1.1 versus Spring JMS API

“

- [Narrator] Let's examine the benefits of using Spring JMS API versus the standard JMS specification. First off, Spring JMS is not a MOM provider but an abstraction layer of APIs to JMS. If you remember from our previous video message-oriented middleware products, MOM, provides implementations of JMS spec interfaces. Spring JMS however, provides an API abstraction so the developer does not have to write all of the standard boilerplate code involved when talking to a MOM. To make this clear, in order to use JMS 1.1 the developer has to first create the JNDI initial context. Then get a ConnectionFactory from the JNDI context. Followed by getting a queue from the queue ConnectionFactory. Then the developer can create the Session object which a Sender or Receiver object can then be created. Finally, the developer can either send or receive a message using the Sender or Receiver object. And then the developer has to close all the JMS resources used for processing the message. Spring JMS…

Contents