You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I know, Jetty "cuts" from URI the part defined in web.xml, that is, in your case "/chat".
If the request is: /chat/whatever, and servlet is mapped to "/chat/*", Jetty will cut out "/chat" leaving only "/whatever" to match into Jersey resources.
Tomcat, for example, does not have this behaviour.
Since the system I am trying to integrate Atmosphere into uses embedded Jetty, I was trying to convert Jersey2-Chat sample to the same logic.
However, when I ran my server and entered a value into the input field, I got "org.atmosphere.websocket.WebSocket - 404 Not Found" on the server.
Here is the code for my server:
My test was using Atmosphere 2.2.0-SNAPSHOT and jersey-container-servlet 2.8.
The only change made to the application.js was to hardcode the URL:
url: 'http://localhost:8084/chat'
so that the index.html can be ran from the file system.
The solution was to change the following line:
to:
At the same time a regular Jersey servlet works with the following line:
Please, make this consistent.
Thank you!
The text was updated successfully, but these errors were encountered: