Bunch of tests for scenario where WebSocket endpoints are decorated with EJBs. This is might be helpful when reading through the EJB integration section of the Java WebSocket API Handbook . This helps validate the behavior which might be a source of confusion since there are two specifications at play here. This is not something which is supported by the WebSocket specification but it is supported by Tyrus (hence you can try this on GlassFish or Payara)
- case 1: A new stateless EJB (from the pool) is allocated for a WebSocket client
- case 2: A stateless EJB (once allocated) remains attached to a WebSocket client throughout it's lifecycle
- case 3: The same Singleton bean instance is used for WebSocket clients (
Sessions) - case 4: A unique Stateful session bean instance is allocated to each unique client
There are two Maven projects
- First one is a simple Java EE (WAR) application with EJB-WebSocket endpoints
- The second one contains the tests
Download the project to your machine. To try things out, first build and deploy the application on on GlassFish or Payara
- cd application
mvn clean install- deploy....
Then, run the tests
- cd tests
mvn test
Note: if required, change the host port here before running the tests