JSR-356 | JSR 356 WebSocket | Websocket library

Is it possible to have all 3 (Websocket, REST Servlet, and a File server) all on the same port?

I've been going through the web finding lots of examples of partial solutions, but the Jetty setup has so many variations that it's hard to determine what will work for me.

I'd prefer to use JSR-356 websocket api rather than the Jetty proprietary, in case I have to move to a different server later.

I want to deploy a spring boot application on weblogic. I have this error:

Erreur javax.servlet.ServletException: Not running on Jetty, JSR-356 support unavailable Erreur Not running on Jetty, JSR-356 support unavailable

Spring boot version 1.5.20 / weblogic Version 12c

can you help me???

code of main

I'd like to deploy webapp, packaged as WAR having web.xml in it, to Jetty server.

Within that app, I'd like to be able to have a JSR-356 specified javax websocket endpoints configured. I prefer, that those endpoints to be provided via ServerEndpointConfig, not an annotation scan.

There are many resources exemplifying that with an embedded Jetty, utilizing already famous WebSocketServerContainerInitializer.configureContext(context); API. I can't do that, obviously.

There are others, jumping directly to ServletContextListener and obtaining the ServerContainer via famous context.getAttribute("javax.websocket.server.ServerContainer"). So far I'm getting pretty much NULL via this API, so obviously container is not added.

What is that bit of configuration that is missing? Can it be done, preferably, via web.xml? If it is about config files like jetty.xml or jetty.ini - example would be nice, again, preferably for xml syntax.

As per answer below (the accepted one) and as I've actually tried to describe here - the known way of configuration is absolutely working just fine. Saying known I mean either by adding --module=websocket to some *.ini file for a non-embedded Jetty, or by calling WebSocketServerContainerInitializer.configureContext for an embedded one.

So rephrasing the question: is there any experience/knowledge from someone to enable websocket module by purely XML based configuration?

Note: This is a cross post because I wasn't sure if this was a technical issue or a bug so the bug can be found here

A couple weeks ago I wrote up a prototype for adding a flexible environment service to our appengine project that is primarily standard environment services. The prototype was based on the java quickstart sample "HelloworldSpringBoot" with some minor modifications.

After my success with the prototype I moved over to a more production set of code for this service, developed it for a couple weeks and attempted to deploy on Jan 12th, 4 days ago. The app refused to start and after several attempts at simplifying the app to just a single route I could not get the app to start.

I switch back to the prototype code, deployed to the original project that code was working in and am seeing the same behavior where the app is not starting.

There is no one error message to point to so I have a couple that I'll list here that may be the culprit.

The first is the most obvious, but may be a generic catch-all:

I am in the process of upgrading our jetty from 9.2.24 to 9.4.10, for an app that works extensively with websockets.

I have an existing test (junit) that sets embedded jetty, registers to it rest resource and websocket servlet and then tests to see if they can be accessed.

The test works perfectly well when jetty is at version 9.2.24. An attempt to move to version 9.4.10 with the very same code fails with

I am trying to convert a springboot project to run on GAE. So far, I am able to connect the project to cloud sql locally.

However, when making the conversion to app engine standard(to deploy it) following several guides/tutorials such as

https://codelabs.developers.google.com/codelabs/cloud-app-engine-springboot/index.html?index=..%2F..%2Findex#4

I see the following exception whenever I start the GAE dev server, or deploy.

How do I properly close a websocket and and provide a clean, informative response to the client when an internal error occurs on my server? In my current case, the client must provide a parameter when it connects, and I am trying to handle incorrect or missing parameters received by OnOpen.

This example suggests I can just throw an exception in OnOpen, which will ultimately call OnError where I can close with a reason and message. It kinda works, but the client only receives an EOF, 1006, CLOSE_ABNORMAL.

Also, because I have found no other discussion, I can't tell what might be best practice.

I'm using the JSR-356 spec, as follows:

My current web server is embedded Jetty 9.1.5. It works well with JSR-356 to create websocket. These days, I am trying to upgrade to Jetty 9.4.1. Everything works nicely except websocket.
My code like below:

1. Embedded Jetty and Websocket libs:

...