Expose Spec ServerContainer.upgrade() API
#6965
Assignees
Labels
Comments
joakime
added
Enhancement
Bug
joakime
changed the title
ServerContainer.upgrade(HttpServletRequest, HttpServletResponse, ServerEndpointConfig, pathParamMap) APIServerContainer.upgrade() API
lachlan-roberts
added a commit
that referenced
this issue
Oct 7, 2021
Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Oct 7, 2021
Signed-off-by: Lachlan Roberts <[email protected]>
This was referenced Oct 7, 2021
This was
linked to
pull requests
Oct 20, 2021
lachlan-roberts
added a commit
that referenced
this issue
Oct 21, 2021
…ammaticUpgrade Issue #6965 - support programmatic upgrade for javax/jakarta websockets (9.4)
lachlan-roberts
added a commit
that referenced
this issue
Oct 21, 2021
…rammaticUpgrade Issue #6965 - support programmatic upgrade for javax/jakarta websockets (10)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
9.4.x +
Description
The upcoming
jakarta.websocket.server.ServerContainer.upgradeHttpToWebSocket(Object httpServletRequest, Object httpServletResponse, ServerEndpointConfig sec, Map<String,String> pathParameters)from jakartaee/websocket#375 has shown industry adoption of this API in other containers.
spring-framework is using this pattern for all other containers (glassfish, tyrus, tomcat, undertow, weblogic, and websphere currently).
We need to implement this all the way back to Jetty 9.4.x.
The text was updated successfully, but these errors were encountered: