Martijn,
On 16/08/2012 11:37, martijnverburg_at_gmail.com wrote:
> Hi all,
>
> As part of the Adopt a JSR program (http://java.net/projects/adoptajsr)
> we're looking to run a JMS 2.0 workshop that will have 20-25 day-today
> developers use the latest version of the RI and give some meaningful
> feedback.
>
> Folks like Colin Crist (and hopefully Tim Fox) will be mentoring each
> group.
This sounds really great...
> So a few questions for the spec lead / EG:
>
> 1.) Is there a binary RI we can use? (some sort of Glassfish
> implementation I assume). Or so we build one from source out of SVN?
The RI will be Open Message Queue (for the standalone JMS provider) and GlassFish (as part of a full Java EE 7
implementation) and will follow the existing open source processes of those projects.
Implementation of JMS 2.0 features in those projects is in progress at Oracle. I would expect an initial implementation
containing some but not all features to be available for JavaOne USA (end Sept), so if you want to actually run some
software then I would suggest you aim to hold your workshop after then. The JMS 2.0 Public Draft is also due about then. (*)
>
> 2.) Are there any test frameworks/stubs/harnesses that are already used
> by the community?
I'm not sure what kind of thing you have in mind, but there's nothing for JMS 2.0 currently.
>
> 3.) Are there any particular areas that the EG are concerned about in
> terms of day-to-day developers using current draft of the spec? We tend
> to setup test scenarios that the developers need to pass and then
> simply observe them using the new API..
I'm not sure quite how to answer this, but I would invite you to look at the what's new section of the current draft.
One of the biggest changes is the new JMSContext API, and support for injection of JMSContext objects in Java EE.
However these are intended for ease-of-use rather than to support any particular use case that couldn't be supported before.
Nigel
(JMS 2.0 spec lead)
>
> Cheers,
> Martijn
(*) An Oracle lawyer has just tapped me on the shoulder to remind me to say that nothing I say here should be taken as a
formal commitment by Oracle (my employer) to deliver anything.