WebSockets not working without WebApp

Question

This works:

String webappDir = "...";
context = tomcat.addWebapp("/", new File(webappDir).getAbsolutePath());

This doesn't:

context = tomcat.addContext("/", new File("").getAbsolutePath());

I don't really need a webappDir in this instance because I am not serving any JSP pages or client-side resources, I'm simply using response.getWriter().println(...); server-side only.

There is no exception being thrown, the websocket simply does not open.

Can I assume that this is a tomcat bug?

Answer 1

well, those two are completely different function. If you look at the javadoc for the function addContext, you can see that, you need to setup the context to be able to use websocket. this is retrieved from the api doc.

Add a context - programmatic mode, no default web.xml used. This means that there is no JSP support (no JSP servlet), no default servlet and no web socket support unless explicitly enabled via the programmatic interface.

So, in your case, I guess you can follow the test case in this link how to add an end point into the context.

As for whether you can assume that this is a bug or not. Personally, I don't think this is a bug as the developer itself already mention that they don't provide the web socket connection. But, to make sure, you may contact them and ask ;).

Answer 2

If you look into the tests (test/org/apache/tomcat/websocket in the source code), they do

tomcat.addContext("", null);

Note that passing null instead of a context path needs a recent Tomcat 8 (no older than several months). The current version is 8.0.22.

Can I assume that this is a tomcat bug?

The rule "before filing a bug" is to ask on the users' mailing list, not on stackoverflow.