|Re: Virgo Tomcat 3.6.3 - Websocket JSR 356 - 404 error? [message #1693194 is a reply to message #1691880]
||Wed, 22 April 2015 10:49
| Patrick Payer
Registered: August 2014
I'm not that sure anymore, that I'm facing the same problem. I've created a new Websocket example. It's totally basic. I've attached both, the example with the ServerEndpoint and the client example I used.
As long as the manifest.mf looks like this, it works perfectly fine on Virgo 3.6.3 with Gemini Web bundles 2.2.6
But I need to specify some OSGi specific manifest headers. As soon as I add an OSGi specific manifest header (e.g. "Bundle-ManifestVersion: 2"), Virgo does not log this line anymore:
"Starting web bundle 'RMWEBSOCKET_SERVER' version '0.0.0' with context path '/RMWEBSOCKET_SERVER'."
When I try to connect to the endpoint with my client after that, it throws a 404 Error.
When I try to set a Web-ContextPath manifest header (e.g. "Web-ContextPath: resman"), Virgo logs the context path line again.
"Starting web bundle 'RMWEBSOCKET_SERVER' version '0.0.0' with context path '/resman'."
But when I try to connect to the endpoint via the new URI ("ws://localhost:8080/resman/resmanep") I also get a 404 Error. So it seems, as soon as OSGi comes into play, Websockets does not work anymore.
Could this be a similar issue like your web fragment issue? Or am I facing a completely different issue?
Powered by FUDForum
. Page generated in 0.02541 seconds