JMS 2.1

In August 2014, Oracle proposed the development of JMS 2.1, and submitted JSR 368 in accordance with the Java Community Process. It was intended that JMS 2.1 would form part of java EE 8.

An expert group was formed which worked for most of 2015. The specification lead was Nigel Deakin.

In October 2015 an Early Draft was published for public review. This included a new chapter on flexible JMS message-driven beans. Work continued and the proposed improvements to JMS message-driven beans were further refined and improved.

In early 2016 Oracle announced that it was re-assessing its priorities and work on developing JMS 2.1 halted. In November 2016 Oracle formally proposed that the JSR be withdrawn.

Oracle confirmed that JMS would remain part of Java EE 8, but the existing version JMS 2.0 would be used rather than a new version 2.1.

This page contains historical information about JMS 2.1, including the most recent version of the proposals for improving JMS MDBs.

Historical information about JMS 2.1

• The initial proposals for JMS 2.1 are summarised in JSR 368
• The JMS 2.1 early draft was released in October 2015. This included a new chapter on flexible JMS message-driven beans.
• JMS spec lead Nigel Deakin gave a presentation at JavaOne in October 2015 “What’s coming in JMS 2.1”. Download the slides. Watch the video. This included a summary of what was in the early draft, together with some other ideas.
• After the early draft was released, the expert group continued work on improving and refining its proposals for flexible JMS MDBs.
  • The latest thinking is summarised in Flexible JMS MDBs: method annotations (version 5). The corresponding API interfaces and annotations can be seen in the source code repository here.
  • Older versions of these proposals are version 1, version 2, version 3 and version 4_.
• The spec lead also made some proposals for CDI Managed Beans as JMS listeners.
  • JMS Listener beans: summary of comments summarises and discusses the comments received.
• The expert group held one face-to-face meeting in October 2015: JSR 368 Meeting 1 at JavaOne 2015.
• The JMS 2.1 plan contains a list of the features that were planned for JMS 2.1.
• The JMS 2.1 Planning Long List contains a classified list of all the open issues that were in the JMS issue tracker at the time that JMS 2.1 was being developed. This includes many issues that were not expected make it into JMS 2.1.
• All these issues are also recorded in the JMS spec issue tracker.

JMS 2.1 schedule

This is a historical record of the JMS 2.1 schedule before work on JMS 2.1 ceased and JSR 386 was withdrawn

This was based in the schedule for the Java EE platform at the time.

Related pages

• How to join the JSR 368 (JMS 2.1) Expert group (Retained for historical purposes only)
• JSR 368 Expert group nominations (Retained for historical purposes only)