Currently registering a WebSocket via Whiteboard fails due to different reasons:
The annotation-scan in the tracker fails due to different identities of the class used to check for the annotation.
Jetty - If 1. is fixed the HttpServiceStarted times out
Undertow - If passed 2. a javax.websocket.DeploymentException occurs claiming the class is not annotated correctly (probably same reason as for 1)
this fails because the Jetty adapter never handles the availability of WebSockets. Jetty must be telled to enabled a (Websocket)ServerContainer and provide the attribute in the ServletContext.
Using Undertow with Whiteboard websockets gets (literally) one step further
this call will end up ServerWebSocketContainer (Undertow) which is not able to compare the existing Annotations with each other because they both live in different classloaders (the bundle with the websocket-class and the undertow-lib).
Furthermore HttpContextStarted is missing an implementation for unregisterWebsocket.