by different web containers (like Apache Tomcat)  Native WebSocket works only when both the browser and the web containers support WebSocket technology. There are no plans to add support to fallback wicket-native-websocket-jetty9 ... • for Jetty 7.x and 8.x org.apache.wicket wicket-native-websocket-jetty implementation) org.apache.wicket wicket-native-websocket-tomcat ... • for JSR356 complaint implementations

by different web containers (like Apache Tomcat)  Native WebSocket works only when both the browser and the web containers support WebSocket technology. There are no plans to add support to fallback Jetty 9.0.x 241 org.apache.wicket wicket-native-websocket-jetty9 ... • for Tomcat 7.0.27+ (the old, non-JSR356 implementation) org.apache.wicket wicket-native-websocket-tomcat ... • for JSR356 complaint implementations

by different web containers (like Apache Tomcat)  Native WebSocket works only when both the browser and the web containers support WebSocket technology. There are no plans to add support to fallback dependency Add the following dependency to your application to get access to the wicket-native-websocket API on any JSR356 compliant application server (at the moment are supported: Tomcat 8.0+, Tomcat Wildfly 8.0.0+): org.apache.wicket wicket-native-websocket-javax 228 ... • for Spring Boot applications

by different web containers (like Apache Tomcat)  Native WebSocket works only when both the browser and the web containers support WebSocket technology. There are no plans to add support to fallback dependency Add the following dependency to your application to get access to the wicket-native-websocket API on any JSR356 compliant application server (at the moment are supported: Tomcat 8.0+, Tomcat Wildfly 8.0.0+): org.apache.wicket wicket-native-websocket-javax 227 ... • for Spring Boot applications