Nigel,
In general, I'm good with the changes in the spec; I think there's just
some minor clean up in order. Some items jumped out at me,
First was this line (page 52) *Messages with a later delivery time may be
delivered after messages with an earlier delivery time. *I feel like this
should be a "shall" or a "should" rather than a may, unless the intention
is to make this an optional feature. I would have assumed this to be a
required feature, if the delivery time is set.
Also, section 4.9, page 60, JMS Exception is the base class for all checked
JMS exceptions sounds more appropriate here. Likewise, JMS Runtime
Exception is not listed under section 7 and should be.
Section 5.9, page 65, *A message must not be returned by a QueueBrowser
before its delivery time has been reached.* I feel like this shouldn't be
a requirement for the browser - it should show all available messages on a
queue regardless of ready to deliver or not. Perhaps I missed that part of
the discussion when we were talking about delivery time.
It also feels like chapter 9 is out of place. Perhaps it was simply in the
order of the original spec? I think it should be the last chapter, or
merged with 11.4 as a new chapter, this way we can consolidate all demo
code into a single chapter.
Regards,
John
On Fri, Dec 7, 2012 at 3:59 PM, Nigel Deakin <nigel.deakin_at_oracle.com>wrote:
> In accordance with the Java EE schedule published several months ago, the
> time has come for us to checkpoint the work we have done so far on JMS 2.0
> and publish a public draft for formal review.
>
> (The complete JMS 2.0 schedule is here:
> http://java.net/projects/jms-**spec/pages/Home#JMS_2.0_**schedule<http://java.net/projects/jms-spec/pages/Home#JMS_2.0_schedule>)
>
> I've also taken a copy of the latest draft specification and javadoc and
> uploaded them as "release candidate 1" to the project downloads area at
> http://java.net/projects/jms-**spec/downloads/directory/**PublicDraftRC1<http://java.net/projects/jms-spec/downloads/directory/PublicDraftRC1>
> .
>
> You can also browse the API docs online at
> http://jms-spec.java.net/2.0-**SNAPSHOT/apidocs/index.html<http://jms-spec.java.net/2.0-SNAPSHOT/apidocs/index.html>
>
> I would like to submit these to the JCP admins before the holidays, so
> could you all please review the spec and API docs and state whether or not
> you think this is fit to be published formally as the public draft? Please
> respond by Wednesday 19th December.
>
> Of course I'd also welcome any comments or questions. If you see any
> errors or typos please let me know - I'll update the draft as needed over
> the next week or so.
>
> One weakness of the document in its current form is that the simplified
> API is still mostly confined to its own section at the end rather than
> being integrated with the rest of the specification. I have deliberately
> avoided doing that so far to make it easier for people to see what's
> changed. However I do plan to restructure the document (essentially moving
> blocks of text around) before the final release.
>
> Appendix B.5 lists the significant changes in the specification. The whole
> document also has change bars.
>
> Please also take a look at the planning page at
> http://java.net/projects/jms-**spec/pages/JSR343Planning<http://java.net/projects/jms-spec/pages/JSR343Planning>
> This lists all the JIRA issues that have been incorporated into the public
> draft, and all those which have not. Those which have not will mostly be
> rolled forward for consideration for JMS 2.1.
>
> Nigel
>
>
>