[KARAF-7544] Upgrade to Jetty 10 and Pax Web 9

• Type: Story
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Grzegorz Grzybek
• Reporter: Grzegorz Grzybek
• Created: 06/Sep/22 10:08
• Updated: 19/Dec/23 18:06

Description

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)

Issue Links

• is blocked by: KARAF-7764 Require Java 11 to build karaf.git
• is blocked by: KARAF-7766 Require Java 11 to launch Karaf
• relates to: KARAF-7754 Require Java 11 at build and runtime