[
https://issues.apache.org/jira/browse/KARAF-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797885#comment-17797885
]
ASF GitHub Bot commented on KARAF-7544:
---------------------------------------
jbonofre commented on PR #1809:
URL: https://github.com/apache/karaf/pull/1809#issuecomment-1859049339
FYI: it's what we had before but we changed that as Jetty and servlet api is
provided by Pax Web. However, for backward compatibility we add a meta feature.
In Karaf 4.5.x, we can completely remove `jetty` feature from Karaf and use
`pax-web-jettty` from pax web instead.
> Upgrade to Jetty 10 and Pax Web 9
> ---------------------------------
>
> Key: KARAF-7544
> URL: https://issues.apache.org/jira/browse/KARAF-7544
> Project: Karaf
> Issue Type: Story
> Reporter: Grzegorz Grzybek
> Assignee: Grzegorz Grzybek
> Priority: Major
>
> I've prepared Pax Web branch to release Pax Web 9 with Jetty 10 upgrade
> (JDK11+). (see: https://github.com/ops4j/org.ops4j.pax.web/issues/1743)
> With few tweaks, Karaf 4.4.2-SNAPSHOT works well with the above dependencies,
> with few restrictions:
> * I've generally upgraded Servlet API jar/bundle used by Karaf to version 4
> * {{StandardFeaturesTest.installAriesBlueprintWebFeature}} and
> {{RestExampleTest.testWhiteboard}} need a _compatibility bundle_ for Servlet
> API, so {{javax.servlet}} package is exported with version 3.1.0 (for
> blueprint.web and aries.jaxrs bundles)
> * {{CamelExampleTest}} needs some polish, because I see that asm 5.0.4 bundle
> is installed from Camel features and it doesn't work with JDK17
> * {{PaxCdiFeaturesTest}} should be removed (IMO), because Pax CDI is no
> longer maintained - Pax Web works well with Aries CDI
> * I've changed all {{<javase>}} elements of karaf-maven-plugin configuration
> to {{<javase>11</javase>}}
> * {{WebSocketExampleTest}} no longer works, as it uses
> {{org.eclipse.jetty.websocket.api.annotations.WebSocket}} and
> {{org.eclipse.jetty.websocket.servlet.WebSocketServlet}} which are not
> available in Jetty 10 - however Pax Web 8+ itself fully works with JSR356
> compatible web sockets (using ServletContainerInitializers for Jetty, Tomcat
> and Undertow)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
