JMS 2.0 is the first update to the JMS specification since
version 1.1 was released in 2002. One might think that an API that
has remained unchanged for so long has grown moribund and unused.
However, if you judge the success of an API standard by the number
of different implementations, JMS is one of the most successful
In JMS 2.0, the emphasis has been on catching up with the
ease-of-use improvements that have been made to other enterprise
Java technologies. While technologies such as Enterprise JavaBeans
or Java persistence are now much simpler to use than they were a
decade ago, JMS had remained unchanged with a successful, but
rather verbose, API.
The single biggest change in JMS 2.0 is the introduction of a new
simplified API for sending and receiving messages that reduces the
amount of code a developer must write. For applications that run
in WebLogic server itself, the new API also supports resource
injection. This allows WebLogic to take care of the creation and
management of JMS objects, simplifying the application even
Other changes in JMS 2.0 asynchronous send, shared topic
subscriptions and delivery delay. These were existing features
WebLogic which are now available using an improved, standard, API.
To find out more about JMS 2.0, see this 15 minute audio-visual slide presentation.
Read these two OTN articles:
See also Understanding the Simplified API Programming Model in the product documentation
In a hurry? See Ten ways in which JMS 2.0 means writing less code.