|Re: [jetty-users] Jetty and WebSockets|
that's exactly as I have done, but it seems that JettyWebSocketServlet never gets executed, for example if I add some log on the configure override method, that one is never executed. when the server start, maybe it does´t get executed until the first request or something like that?? is there any simple way to test the web socket? lets say pasting the url on a web browser that supports them?? or is there any thin client out there to check it?any other pointer??thanks a lot!
On August 20, 2013 at 2:35:52 PM, Joakim Erdfelt (joakim@xxxxxxxxxxx) wrote:hine.hostname" is your server's host name (or ip)The "port" is the non-SSL port you have configured your server on.The "webapp.context" is the context path where you deployed your web applicationand "/websockets/" is the request path you have specified in your servlet-mapping
Back to the top