The text of each proposed change for the JMS 2.0 errata has now all been formally recorded in JIRA and (except for some
trivial typos) circulated to this email list.
I've updated the list of issues on JMS 2.0 errata wiki page:
https://java.net/projects/jms-spec/pages/JMS20RevA#Proposed_content with links to the text of each proposed change.
I originally planned to submit these changes to the JCP on 19th December but to give a final opportunity for comments I
have deferred this by three weeks until Friday 9th January. Here, then, is a final invitation to make comments on the
proposed changes.
I've updated the "proposed timescales" table at
https://java.net/projects/jms-spec/pages/JMS20RevA#Proposed_timescales
to reflect the revised plan.
Just to repeat what I've said earlier: the significant changes are
JMS_SPEC-125 Define whether a JMS provider should call reset after sending a BytesMessage asynchronously
JMS_SPEC-155 JMS 2.0 introduced incompatible changes to createSession(bool,int)
JMS_SPEC-157 JMS 2.0 introduced an incompatible restriction on creating two sessions per connection in Java EE
JMS_SPEC-158 JMS 2.0 introduced incompatible changes to Connection.stop and close and Session.close
In the latter three cases, I'm proposing to make changes to the classic API only and leave the simplified API unchanged.
If you have views on this (especially for JMS_SPEC-158) please say so.
Nigel