You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Grzegorz Grzybek (Jira)" <ji...@apache.org> on 2022/09/06 10:09:00 UTC

[jira] [Created] (KARAF-7544) Upgrade to Jetty 10 and Pax Web 9

Grzegorz Grzybek created KARAF-7544:
---------------------------------------

             Summary: 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


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)