JMS 2.0 (part of the Java EE 7 Platform) introduced lots of nice features. One of these was the ability to declare JMS resources for automatic deployment.
Pre Java EE 7
- Inject Connection Factory using @Resource
- Lookup Destination (Queue/Topic) using @Resource
- Pull out the Session object and use it to create the Message, Message Producer and send the message
Most importantly, you had to make sure that the resources i.e. the Connection Factory and the physical destinations were configured in your application server in advance
In the Java EE 7 era ….
You can leverage JMS 2.0 goodies
- Use injected JMS Context (in most of the cases) to ease the sending process with less boilerplate code
- Most importantly, you can declaratively configure auto provisioning of JMS Resources using annotations or deployment descriptors
Let’s look at the new JMS 2.0 annotations in action. You can also pick up this Maven project on Github and deploy it in your favourite IDE
Used to declare one or more connection factories
Used to declare one or more physical destinations (queues or topics)
Oh and you can also use XML
These can be a part of the web deployment descriptor (web.xml) or the EJB deployment descriptor (ejb-jar.xml)
There are several ways to use this feature
- Declare your JMS resources using a @Startup powered @Singleton EJB
- You can also declare it on a Servlet or any CDI managed bean for that matter
What’s the point of all this ?
The container/Java EE application server makes sure that the JMS artefacts are available to your application logic on-demand
- It’s valuable in PaaS, microservices, dockerized and any other environment which heavily leverage automated deployments
- Good for automated testing
- It’s one less item to think about and configure!
- JMS 2.0 specification document
- They have a twitter account too !
- The Aquarium Blog for all things Java EE