Skip to main content
Last updated November 05, 2013 12:05, by nigeldeakin
Feedicon  

Java Message Service Specification

Welcome to the website for the development of the Java Message Service (JMS) specification. JMS 2.0 was released on 21 May 2013. For more information see the JMS 2.0 Final Release page.


JavaOne 2013

The slides from the conference session Easier Messaging with JMS 2.0 (held on 23 Sept 2013) may be downloaded here . An audio recording will be published on the JavaOne website after the conference ends.

JMS 2.0

JMS 2.0 was finally released on 21 May 2013. See the JMS 2.0 Final Release page for information on where to find the specification and API documentation. That page also contains information on the new features in JMS 2.0, where to download the reference implementation, and provides links to various useful articles about JMS 2.0.

JMS 2.1

The name informally given to the next release of JMS is JMS 2.1. If you'd like to make a suggestion or proposal as to what should be in the next version of JMS please log an issue in the issue tracker or send an email to the community email alias.

For more information about how to contribute to the development of the JMS specification please see Getting Involved below.

Proposals and suggestions are being captured on the JMS 2.1 planning page.

About the development of the JMS specification

The Java Message Service (JMS) specification was first released in 1998, at the dawn of Java EE, with a major update in 2002. It then remained unchanged during the decade that followed. Meanwhile, technology evolved and many vendors pressed ahead with enhancements outside the specification. During that time, the rest of Java EE evolved significantly, with improvements and new features added. Despite the lack of development of the specification, JMS continued to be a popular and successful standard, with numerous competing implementations, both standalone and as part of complete Java EE stacks, and open and closed source.

On 1st March 2011 a Java Specification Request (JSR) was submitted to the Java Community Process which proposed that a new version of the JMS specification be developed. This is JSR 343: Java Message Service 2.0.

On 21 May 2013 JMS 2.0 was released. This major update introduces a new simplified API and adds support for the injection of JMS connections into Java EE applications. It forms part of Java EE 7. Now that JMS 2.0 is released, JSR 343 moves into maintenance mode.

The purpose of this website is to support the continuing development of the JMS specification. Currently it is focussed on JSR 343 by hosting its mailing lists, issue tracker, wiki and any other resources that are required. It runs in conjunction with the official JSR 343 page on the JCP website which is used mainly to conduct the formal aspects of the JSR.

This website is a project hosted by java.net. It is administered by the JMS 343 maintenance lead. To get the best out of this website, to join the mailing lists and use the issue tracker, you need to register with java.net and log in.

The JSR 343 maintenance lead is Nigel Deakin (Oracle). You'll find a list of the expert group members on the official JSR 343 page on the JCP website .

JMS 2.0 schedule (historical)


Also see the JMS 2.0 Planning page

Stage Initial plan
(Feb 2011)
Current plan
(updated 1 Nov 2012 6 Feb 2013)
Actual
JSR approval March 2011 March 2011
Expert group formation March 2011 May 2011
Early draft review Q3 2011 28 Feb - 29 Mar 2012
Submission of Public Review Draft to the JCP 19 Dec 2012 19 Dec 2012
Start of Public Review 3 Jan 2013 3 Jan 2013
End of Public Review 4 Feb 2013 4 Feb 2013
Completion of JCP Public Review Ballot 18 Feb 2013 18 Feb 2013
Submission of Proposed Final Draft to the JCP 20 Feb 2013 20 Feb 2013
Submission of Materials for Final Ballot to the JCP 20 Mar 2013 20 Mar 2013
Start of Final Ballot 26 Mar 2013 26 Mar 2013
Completion of Final Ballot 8 Apr 2013 8 Apr 2013
Release of Spec, RI, TCK 15 Apr 2013 30 Apr 2013 22 April 2013 21 May 2013

This was based in the schedule for the Java EE platform

Getting involved

Here are some ways to get involved in the development of the JMS specification:

  • If you'd like to observe what is going on, participate in discussions with other interested users and observe what the expert group is doing, join the users@jms-spec.java.net mailing list.
  • If you'd like to submit proposals for consideration by the expert group, log them as issues in the JIRA issue tracker. Please read How to use the issue tracker]. We're interested in comments on JMS 2.0 as well as proposals for a future release.
  • Since JSR 343 is now in maintenance mode we're not currently seeking applications to join the expert group. A new full release of JMS will require a new JSR and a new expert group.

Mailing lists

Mailing lists connected to the jms-spec.java.net project


Email address Purpose Access
users@jms-spec.java.net Mailing list for observers for general discussion about the JMS specification.
Discussions on the mailto:jsr-343-experts@jms-spec.java.net mailing list are forwarded to this list to allow observers to monitor the discussions of the expert group.
Before you can receive messages from or post messages to this list, you need to join the jms-spec.java.net project as an observer and then subscribe to this list.
Online archive of past messages
jsr343-experts@jms-spec.java.net Mailing list for members of the JSR 343 expert group.
Discussions on this mailing list are forwarded to users@jms-spec.java.net to allow observers to monitor the discussions of the expert group.
For reasons of transparency expert group discussions should use this list where possible.
For formal EG business, or where a discussion needs to be kept private to the EG, use jsr-343-eg@jcp.org instead.
Before you can receive messages from or post messages to this list, you need to be a member of the JSR 343 expert group, join the jms-spec.java.net project as an content developer and then subscribe to this list.
Online archive of past messages
issues@jms-spec.java.net Mailing list for JIRA issue notifications
Additions and updates to the issue tracker are automatically sent to this list
Before you can receive messages from or post messages to this list, you need to join the jms-spec.java.net project as an observer and then subscribe to this list.
Online archive of past messages
How do I join the jms-spec.java.net project as an observer?
Simply click on Join this project on the left, and you'll be instantly get an observer role on the project. You'll need to be logged into java.net. This will also add this project to your My Projects page.
How to I subscribe to a mailing list?
After joining the project, navigate to java.net/projects/jms-spec/lists, find the list you want to subscribe to, and press the Subscribe button.
I tried to reply to an email but it was rejected. Why?
If you subscribe to users@jms-spec.java.net you'll automatically receive a copy of all emails sent to the expert group. You're welcome to reply to any email with a comment. However if you are not a member of the expert group you'll need to change the recipient to users@jms-spec.java.net before replying, otherwise your email will be rejected. The expert group will see all emails sent to users@jms-spec.java.net.

Mailing lists connected with JSR 343 and managed by the JCP


Email address Purpose Access
jsr-343-observers@jcp.org Mailing list for observers of JSR 343.
Registered observers of JSR 343 are automatically subscribed to this list.
There is currently no online archive of past messages.
Please do not use this list, use users@jms-spec.java.net instead.
jsr-343-eg@jcp.org Mailing list for members of the JSR 343 expert group.
Expert group members will use this for formal JCP business or when discussions need to be kept private to the EG.
For reasons of transparency expert group discussions should the more public list jsr343-experts@jms-spec.java.net where possible.
Registered members of the JSR 343 expert group are automatically subscribed to this list.
There is currently no online archive of past messages.

Issue tracker

Comments and changes to the JMS specification will be managed using the JIRA issue tracker.

If you would like to propose a change to the JMS specification, please create an issue containing a description of the proposed change, or search for an existing issue and add a comment. You need to sign up for a java.net account and login first.

How to create an issue

Here are some guidelines to follow when creating a new issue:

  • Please don't combine unrelated subjects in the same issue. Create a separate issue for each.
  • Issue Type: .Choose one of Bug, New Feature, Task or Improvement from the pop-up menu.
    • Bug: There is a problem or error in the spec, API or javadocs
    • New Feature: Use this to suggest a new feature which is not in the existing spec, API or javadocs
    • Task: Please don't use this
    • Improvement: An improvement or enhancement to an existing feature of the spec, API or javadocs
  • Summary Please enter a meaningful one-line summary of your issue
  • Priority: Please don't change this
  • Component/s We will use this in the future to allow you to categorise your issue
  • Affects version/s Please specify which version of the JMS specification your comment relates to. Normally this will be 1.1, the latest released version.
  • Environment: Please leave blank
  • Description: Please describe your issue in as much detail as you wish. You can add comments later.
  • Original Estimate: Please leave blank
  • Attachment: There shouldn't be much need to use this, but if necessary you can upload files here
  • Issuezilla Id: Please leave blank
  • Status Whiteboard: Please leave blank. We may start using this field in the future.
  • Tags: Please leave blank. These should only be set by the project administrators, so if you set these yourself you'll confuse things.

Public ideas whiteboard

As part of an initiative to lower the barrier for community members to submit ideas (both for now and the future), we'd like to invite you to post your suggestions for JMS to the Public ideas whiteboard. Just follow the link and click 'Edit Page' on the left of the screen. You need to be logged into java.net and have added yourself as a member of the project.

Procedures and policies

The Java EE Backwards Compatibility Requirements (on the Java EE WIki) describe the requirements to make releases of JMS 2.0 backwards compatible with previous versions.

 
 
Close
loading
Please Confirm
Close