[
https://issues.apache.org/jira/browse/AMQ-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895464#comment-17895464
]
Matt Pavlovich commented on AMQ-9359:
-------------------------------------
[~terjestrand] If we move Servlet to EE10, we need to update all of ActiveMQ to
EE10.
The code doesn't compile yet, so nothing to test ;-) The Jetty migration guide
is pretty good, but there are a number of gaps and the things that change are
scary things like security context patterns, so I don't expect this to be
"quick".
If you are familiar with programming Jetty, you could take stab at updating the
activemq-http module which needs the websocket code refactored for Jetty 12.
> Upgrade to jakarta.servlet-api 6.0.0 & Jetty 12.0.x
> ---------------------------------------------------
>
> Key: AMQ-9359
> URL: https://issues.apache.org/jira/browse/AMQ-9359
> Project: ActiveMQ Classic
> Issue Type: Dependency upgrade
> Reporter: Jean-Baptiste Onofré
> Assignee: Matt Pavlovich
> Priority: Major
> Fix For: 6.3.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> FYI, we don't have any Karaf release supporting jakarta.servlet-api and Jetty
> 11 for now.
> Regarding the timing, we can directly jump to servlet-api 6.x and Jetty 12.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
