Dear experts,
Now that we have finished the 1.0 version of the spec, I'd like to keep
things going here for a while longer.
There's a couple things to do.
Firstly, our Oracle team is starting to think through doing a
maintenance release of the specification. In a maintenance release, we
can't add features or APIs, but we can clarify what is there. We already
have a number of issues that folks have been good enough to file as you
will see on the issue tracker. I know we have implementations that are
working towards passing the TCK that will probably raise some more areas
that need clarifying, and of course when glassfish 4 goes out, we should
get developer feedback, some of which may result in things to put in the
maintenance release.
We have been talking about a maintenance release at the end of this
calendar year, but nothing has been decided. So I'd be interested to
know especially from those of you implementing the spec and running the
TCK what your timeline is. Perhaps coordinating the MR against though
timelines might be beneficial. So, spec implementers, let me know.
Secondly, at some point we will start up the next WebSocket JSR, so if
you have some bright ideas about what that JSR should work on, then
please either file them in JIRA, and/or send them out to the list.
Until we start the new JSR, this list will be the place to discuss the
Java API for WebSocket.
Thirdly, we have an issue about WebSockets and what CDI scope they might
fit into. I just don't know if this is a .next issue, or an issue that
could be resolved in the MR. Since it potentially touches so many specs
(it started as a JMS/WebSocket problem), WebSocket, Servlet Upgrade, EE,
CDI, JMS, then I want to get some input early on that. See next message.
Thanks,
- Danny
--
<http://www.oracle.com> *Danny Coward *
Java EE
Oracle Corporation