We will retain the ServerContainer as a subtype of WebSocketContainer. Programmatic deployment of server endpoints is a container level function specific to server implementations.
Programmatic deployment will require some of the static validity checking of the endpoint to take place at the time of call of the API.
For now, we may need to rely on container specific support to be able to associate the ServerContainer instance with the ServletContext. We haven't made it a goal (yet!) in this project to have the implementations be totally portable across web containers. I'll add this to the list for .next, when we have more implementations to look at to see where there are container specific hooks.
Mark, we will be interested to see how you implement this bootstrap at application deployment time, and will be happy to compare notes when we have it working properly.
I have filed a separate issue (165) on the bootstrap/portability issue so that we can decide, when we have some more implementation experience ourselves and from others, as to how best to address this issue.