The Java Community Process(SM) Program - Community Update - View Community Update Information for JSR# 343

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy

JSR

Community

Expert Group

Community Summary | Community Files

JSR #343 Java^TM Message Service 2.0

Community Summary

The materials on this page are provided by the Maintenance Lead of this JSR for evaluation and feedback.
These materials are not final, and are subject to change as the JSR progresses through the process.

This JSR is being run as a java.net project in order to provide greater transparency to the community. To find out more about JSR 343, and to get involved, please visit jms-spec.java.net where the JSR 343 wiki, mailing lists and issue tracker may be found. Getting started with JMS 2.0

Download and read the JMS 2.0 specification and API docs. See the JMS 2.0 final release page on the JMS spec wiki for more information.
Subscribe to the users@jms-spec.java.net user alias. See How to subscribe.
If you're interested in JMS 2.0 as part of a full Java EE 7 application server, download GlassFish 4.0 and try it. There are some simple examples in the JMS specification itself, on the JMS spec wiki here or you could work through the JMS 2.0 tutorial.
If you're interested in using JMS 2.0 standalone in a Java SE environment (rather than as part of a full Java EE 7 application server), download Open Message Queue 5.0 and try it.

Providing feedback

Send questions about the JMS spec, and requests for clarification, to the user alias (preferred) or directly to the maintenance lead.
If you spot an error or typo in the specification or API documentation please report it directly into the JMS spec JIRA repository (see How to create an issue) or directly to the maintenance lead.
More general comments about the spec (what you liked, what you didn't like, whether you thought the changes were useful and so on) are also very welcome and will help guide the future development of the specification. Please direct them to the user alias (preferred) or directly to the maintenance lead.
It's not too early to suggest what you would like to be in the next version. You can log proposals directly into the JMS spec JIRA repository or you can send them to the user alias (preferred) or directly to the maintenance lead. Suggestions are most useful if they take the form of proposals rather than vague requests that JMS should "do something about foo".

Note the Adopt-a-JSR for Java EE 7 Guidelines

References

JSR 343
Download the JMS 2.0 specification and API docs
Browse the online JMS 2.0 API documentation
JMS specification issue tracker
JMS 2.0 reference implementation as part of Java EE 7: GlassFish 4.0
JMS 2.0 reference implementation standalone for use in Java SE: Open Message Queue 5.0
JMS 2.0 tutorial, part of the Java EE tutorial
See chapter 15 "Examples of the simplified API" in the JMS 2.0 specification.
The JMS 2.0 final release page on the JMS spec wiki