5080 is standard port for our application and work as expected with tomcat connector
org.apache.wicket.protocol.ws.javax.WicketEndpoint#onOpen() is not being called :( maybe tomcat embed jar list used: ecj-4.4.jar tomcat-embed-core.jar tomcat-embed-jasper.jar tomcat-embed-logging-juli.jar tomcat-embed-logging-log4j.jar is not complete :( I guess tomcat-embed-websocket <http://mvnrepository.com/artifact/org.apache.tomcat.embed/tomcat-embed-websocket> should be added :( Will try Thanks for the hint! On 11 November 2014 16:20, Martin Grigorov <mgrigo...@apache.org> wrote: > Hi Maxim, > > > On Tue, Nov 11, 2014 at 11:54 AM, Maxim Solodovnik <solomax...@gmail.com> > wrote: > > > Hello, > > > > I just tried to switch to "javax" websockets (from "tomcat" websockets) > > was was done: > > 1) wicket version was changed to 7.0.0-M4 > > > > good > > > > 2) filter changed > > to org.apache.wicket.protocol.ws.javax.JavaxWebSocketFilter > > > > good > > > > 3) these 2 dependencies added to pom > > <dependency> > > <groupId>org.apache.wicket</groupId> > > <artifactId>wicket-native-websocket-core</artifactId> > > <version>${wicket.version}</version> > > </dependency> > > > > this is not really needed because it is a transitive dependency of > wicket-native-websocket-javax > but it shouldn't cause problems too > > > > <dependency> > > <groupId>org.apache.wicket</groupId> > > <artifactId>wicket-native-websocket-javax</artifactId> > > <version>${wicket.version}</version> > > </dependency> > > 4) Tomcat version is ensured to be 7.0.55 > > > > good > > > > > > Result: "WebSocket connection to > > > > > 'ws://localhost:5080/openmeetings/wicket/websocket?pageId=0&wicket-ajax-baseurl=&wicket-app-name=OpenmeetingsApplication' > > failed: Error during WebSocket handshake: Unexpected response code: 404 " > > > > is port 5080 correct ? I'm asking because it is not "standard" one (80, > 8080) but 5080 should work too > > > > > > No errors in the log on server start and while working > > > > Should this configuration work? or maybe I'm missing something? > > > > It should work. > > Put a breakpoint > at org.apache.wicket.protocol.ws.javax.WicketEndpoint#onOpen() and check > whether it is called by Tomcat > > > > > > We are using "embeded Tomcat", it is started by Red5 (not sure how) maybe > > this is the reason .... > > > > > > > > > > Thanks in advance! > > > > -- > > WBR > > Maxim aka solomax > > > -- WBR Maxim aka solomax
