I'm not going to comment about the TCK, but at least I can give some background / history on websocket.
The difference between websocket 1.0 and websocket 1.1 is the addition of 2 methods (to make lambda support possible).
See:
The websocket project has 2 artifacts.
The jakarta.websocket-client-api-<ver>.jar
This is a client only JAR, for working with standalone websocket clients (not affiliated with a EE container)
The jakarta.websocket-api-<ver>.jar
This is the server + client API, and is also not affiliiated with a EE container.
The Jakarta WebSocket API has no dependency on any other Jakarta EE project.
There should (eventually) be 4 different forms of testing to know if you conform to the Jakarta WebSocket API.
- Server WebSockets in a Servlet container
- Server WebSockets not in an Servlet container. (this exists)
- Client WebSockets in standalone environment with no EE components.
- Client WebSockets as accessed from within a Servlet container.
Any other tests with Jakarta WebSocket API in the mix (such as CDI or security) is out of scope for the Jakarta WebSocket project.
My understanding of the existing TCK tests is that performs a API signature test and performs the suite of tests from #1 and #4 above.
- Joakim Erdfelt
Jakarta WebSocket co-lead
