The JCP executive committee has approved the final release of JMS 2.0. All eligible members voted yes.
Here are the details
http://jcp.org/en/jsr/results?id=5484
You will see that three members added comments to their yes votes:
On 2013-04-07 London Java Community voted Yes with the following comment:
"The LJC supports the technical work done in the context of this JSR, but feels that give the innovations that have
occurred in the messaging space since the release of JMS 1.1 that this JSR could have been more ambitious and broader in
scope. The LJC views the messaging space as one in which further standardisation is possible and desirable, and urges
interested JCP members to explore possibilities in this space."
On 2013-04-07 Keil, Werner voted Yes with the following comment:
"This JSR sets a good example of getting the license right by pointing to the Spec License.
LJC's comment has some point, and one or the other EG Members not having been very actively involved may have been one
reason for a more "evolutionary" state than a giant leap compared to JMS 1.x
However, the messaging space just like Social Media, one of its most vital use cases nowadays is extremely volatile and
driven by the interests of big players more than serious efforts of standardisation. The JSR 357 proposal did
explicitely point to JMS as a related Spec and technology, and had there been a desire for further standardisation in
this area, a JSR like 357 could have helped this one with new incentives. It seems, the industry isn't ready for that at
this time;-)"
On 2013-04-08 IBM voted Yes with the following comment:
"IBM's vote is based on the technical merits of this JSR and is not a vote on the licensing terms. IBM supports
licensing models that create an open and level playing field by allowing third parties to create independent
implementations of Java Specifications and that do not allow individuals or companies to exercise unnecessary control
for proprietary advantage. We support open source as a licensing model for contributions in the JCP, and would hope
others will support this direction. This comment is not necessarily directed at the current business or license terms
for this JSR, however, it is a statement of IBM's preferred licensing model."
The next step is for the spec and Java SE RI to be officially released. Two weeks are allowed for the preparation of the
spec and RI download pages (the main thing is we need to do is make a final build of the RI, including the API jar, with
a version number of 2.0). The planned final release date for JMS 2.0 is 22 April.
Note that the Java EE 7 spec and RI (including the RI for the various Java EE JMS features) will follow a few weeks
behind us; the schedule for the other Java EE specs is at
http://java.net/projects/javaee-spec/pages/Home#Java_EE_7_Schedule
Nigel