Skip to main content
This revision made February 29, 2012 11:57, by nigeldeakin

JSR 343: JMS 2.0 - the next version of the JMS Specification

Welcome to the website for the development of the Java Message Service (JMS) specification. JMS 2.0 is currently being developed through the Java Community Process as Java Specification Request (JSR) 343.


JMS 2.0 Early Draft

The JMS 2.0 Early Draft is now published for formal review. See the JMS 2.0 Early Draft page to find out what's new, how to download the draft, and how to comment.

Other news

5 Oct 2011: Slides from the BOF at JavaOne: JSR 343: What's coming in JMS 2.0
25 Oct 2011: Compatibility guidelines added
17 Nov 2011: Slides from the presentation at Devoxx: What's (probably) coming in JMS 2.0

About JSR 343

The Java Message Service (JMS) specification predates Java EE. Yet since its inception, there has been only one update, and that was in 2002, over eight years ago. Meanwhile, technology has evolved and many vendors have pressed ahead with enhancements outside the specification. Moreover, Java EE itself has evolved over recent years, with improvements and new features added and more in the pipeline for Java EE 7. Meanwhile JMS continues 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.

It's time for a new version of JMS which brings it up to date with the latest developments in Java EE and reflects the considerable experience that has been gained in building and using JMS implementations.

On 1st March 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.

The purpose of this website is to support the 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 will run in conjunction with the official JSR 343 page on the JCP website which will be 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 specification 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 Specification lead is Nigel Deakin (Oracle). You'll find a ist of the expert group members on the official JSR 343 page on the JCP website .

Getting involved

Here are some ways to get involved in the next revision 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.

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.

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.

The JIRA usage page contains detailed notes on how we're using tags to track issues (but please don't set them yourself), and provides some useful queries.

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.

Useful JIRA queries

See the JIRA usage page.

Licence

The business terms for the Specification, Reference Implementation (RI) and Technology Compatibility Kit (TCK) that will apply when JSR 343 is final are specified in section 2.18 of the original JSR request.

Procedures and policies

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

Difference compared to previous revision
__TOC__ == Latest news == ===JMS 2.0 Early Draft === The JMS 2.0 Early Draft is nearly complete and only needs a final review from the expert group before it will be submitted. Here are t

JSR 343: JMS 2.0 - the next version of the JMS Specification

Welcome to the website for the development of the Java Message Service (JMS) specification. JMS 2.0 is currently being developed through the Java Community Process as [http://jcp.org/en/jsr/detail?id=343 Java Specification Request (JSR) 343]. ... ==JMS 2.0 Early Draft == The JMS 2.0 Early Draft is now publishe latest working drafts: [ http://java.net/projects/jms-spec/sources/repository/content/jms2.0/specification/word/JMS20.pdf Latest working draft of the specification ] (Requires jhed for formava.net login)
[
http://java.net/projects/jms-spec/sources/repository/content/jms2.0/target/jms-2.0-javadoc.jar Latest working draft of the javadocs] (Requires javaal review.net login)
Th
. Se following JIRA qury will list all the "issues" included in the Early Draft:
[http://java.net/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ee the [[JMS_SPEC+AND+Tags+%JSR3D+ed20-added Issues included in the JMS 2.0 43Early Draft]
Quite a few issues didn't make it into the Early Draft and have been deferred until the next draft (the Public Draft):
[http://java.net/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+
EarlyDraft|JMS_SPEC+AND+Tags+%3D+pd20-underreview Issues which are not included in the JMS 2.0 Early Draft but will be considered for inclusion in the JMS 2.0 Public DrJMS 2.0 Early Draft paft]
S
geveral]] JMS-related issues affect other specifications and have been submitted to the appropriate expert group:
[h
ttp://java.net/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JMS_SPEC+AND+Tags+%3D+jms20-jsr345 Issues which have been passed to the EJB 3.2 expert group for inclu to find out what'sion in that specification]
[http://java.net/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JMS_SPEC+AND+Tags+%3D+jms20-jsr342 Issues
whichs new, have been passed t howo the Java EE 7 expert group f to dor iwnclusion in that specification]
Other queries
[http://java.net/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JMS_SPEC+AND+resolution+%3D+%22Won%27t+Fix%22+AND+status+%3D+Close
d Issues that have been rejected] (More JIRA queries on the [[JIRAUsage | JIRA usage]] page). '''Commennload the drafts, are welcome'''. You can either send email to the [mailto:users@jms-spec.java.net user list] ([http://java.net/projects/jms-spec/pages/Home#Mailing_lists_connected_to_the_jms-spec.java.net_project how to subscribe]) or you can add a comment to the JIRA issue [http://java.net/projects/jms-spec/pages/Home#Issue_tracker (how]). === and how to comment. == Other news=== 5 Oct 2011: Slides from the BOF at JavaOne: [http://java.net/projects/jms-spec/downloads/download/javaone2011-jms20.pdf JSR 343: What's coming in JMS 2.0
25 Oct 2011: [http://java.net/projects/jms-spec/pages/CompatibilityGuidelines Compatibility guidelines] added
... 25 Oct 2011: [http://java.net/projects/jms-spec/pages/CompatibilityGuidelines Compatibility guidelines] added
17 Nov 2011: Slides from the presentation at Devoxx: [http://java.net/projects/jms-spec/downloads/download/JMS2.0Devoxx2011.pdf What's (probably) coming in JMS 2.0] == WhaOther news== 5 Oct 2011: Slides from the BOF at JavaOne: [http://java.net/projects/jms-spec/downloads/download/javaone2011-jms20.pdf JSR 343: What's coming in JMS 2.0
25 Oct 2011: [http://java.net/projects/jms-spec/pages/CompatibilityGuidelines Compatibility guidelines] added
... 25 Oct 2011: [http://java.net/projects/jms-spec/pages/CompatibilityGuidelines Compatibility guidelines] added
17 Nov 2011: Slides from the presentation at Devoxx: [http://java.net/projects/jms-spec/downloads/download/JMS2.0Devoxx2011.pdf What's (probably) coming in JMS 2.0] == About isJSR happening?343 == The Java Message Service (JMS) specification predates Java EE. Yet since its inception, there has been only one update, and that was in 2002, over eight years ago. Meanwhile, technology has evolved and many vendors have pressed ahead with enhancements outside the specification. Moreover, Java EE itself has evolved over recent years, with improvements and new features added and more in the pipeline for Java EE 7. Meanwhile JMS continues 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.
 
 
Close
loading
Please Confirm
Close