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
If you're interested in JMS 2.0 as part of a full Java EE 7 application server,
download GlassFish 4.0 and try
There are some simple examples in the JMS specification itself, on the JMS spec wiki
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.
Send questions about the JMS spec, and requests for clarification, to the user alias (preferred)
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".