Java API for WebSocket (JSR 356) is going through the JCP maintenance release process as it enters today the Maintenance Review Ballot. This ballot will end in a week on August 4.
The proposed changes are relatively limited but are nevertheless important. In the current specification (1.0), the issue is located in the Session.addMessageHandler(MessageHandler) method which is forcing implementations to get the generic type of the message handler instance. And in some cases, that approach can be problematic (e.g. with lambda based message handler).
To solve this, the 1.1 version of the JSR 356 specification introduces 2 new addMessageHandler() methods (and keep the existing method for backward compatibility). For the complete descriptions of the issue and the 2 new methods, check here.
If everything goes well (i.e. Maintenance Review Ballot passed in time), Tyrus (JSR 356 Reference Implementation) will be updated to reflect those changes and should be integrated in the upcoming GlassFish 4.1 release.
Podcasts & Videos
- Developers Continue to Affirm Strong Support for Java EE 7
- Self-Documented Services Using JAX-RS Analyzer
- Java SE 8 and Java EE 7 in Production at TecSinapse
- Java EE @ ConFoo 2016
- The next VTS round is fast approaching!
- Java EE 7 Proves Effective for Mission-Critical E-Payment Systems
- Java EE @ DevNexus 2016
- Java EE in Practice for Secure Online Voting at Scytl
- Cargo Tracker Java EE 7 Blue Prints Now Running on WebLogic
- Revamping the Security API in Java EE 8