Jakarta WebSocket defines a API for Server and Client Endpoints for the WebSocket protocol (RFC6455).
The plan for the release is to tackle the open issues with a view to implementing as many as possible in the time available. A rough priority order for this being:
None known at this time.
None.
The JDK version required will be aligned with Jakarta EE 10.
The following TCK updates will be required:
The Plan Review Specification Committee Ballot concluded successfully on 2021-05-14 with the following results.
| Representative | Representative for: | Vote |
|---|---|---|
| Kenji Kazumura | Fujitsu | +1 |
| Dan Bandera, Kevin Sutter | IBM | +1 |
| Ed Bratt, Dmitry Kornilov | Oracle | no vote |
| Andrew Pielage, Matt Gill | Payara | +1 |
| Scott Stark, Mark Little | Red Hat | no vote |
| David Blevins, Jean-Louis Monteiro | Tomitribe | +1 |
| Ivar Grimstad | EE4J PMC | +1 |
| Marcelo Ancelmo, Martijn Verburg | Participant Members | +1 |
| Werner Keil | Committer Members | +1 |
| Dr. Jun Qian | Enterprise Members | +1 |
| Total | 8 |
The ballot was run in the jakarta.ee-spec mailing list
Click on the specifications below to access the specification document, Javadoc, Technology Compatibility Kit (TCK), and compatible implementation for each release of the specification.
The Jakarta EE Platform and Profile specifications are the umbrella specifications for the individual specifications. The Jakarta EE Platform includes most of the individual specifications, while the Profile specifications include the individual specifications for developing web platforms and microservices architectures.
Each individual specification describes a standardized way of implementing a particular aspect of an enterprise Java application.