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
- Jersey, from Android to Mainframe
- Unsynchronized Persistence Contexts in JPA 2.1/Java EE 7
- JavaOne Replay: Java EE Game Changers
- Rakuten: Java EE Adoption in One of the World’s Largest Online Financial Systems
- Java EE @ CodeMash 2015
- HTTP/2 is done
- Tyrus and Autobahn|Testsuite compliance
- Manfred Riem Discusses JSF and Java EE MVC on JSF Central Podcast
- The JavaOne 2014 Rock Stars are Here!
- Project Avatar Update