On 05/12/2013 08:33, Johan Compagner wrote: >> >> >> Good. >> >> Remove the tomcat7-websocket.jar library if you do not need it. This >> library (added in 7.0.47, a JSR-356 Java WebSocket 1.0 implementation) >> has a ServletContainerInitializer and thus forces Tomcat to perform >> annotation scanning. >> >> > Does anyone know why this wasn't done by using services? (SPI) > So that we can directly point to a class that is the websocket or point to > a class that registers the websockets?
The Java WebSocket 1.0 specification requires this behaviour. As has been pointed out previously, there really should be a way for a web application to disable a container provided SCI if it knows it doesn't need it. The specification doesn't currently allow this. A Tomcat specific feature to do this is on my TODO list. I'm thinking something like a regular expression of SCI implementation classes to exclude configured on the Context. As always, patches welcome. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
