-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare Pax Web version using JakartaEE 10+ API #1802
Comments
Changes in XSD (6.0):
|
No point of using |
Jetty 11 seems to be only Servlet API 5.0.0... (so for example no |
Jetty 12 Beta (already available in Maven Central) is Servlet 6 implementation. |
(Dead)lock in HTTP/2 tests for Jetty (need to investigate writer closing in PUSH promises):
|
…o be verified later. for now it just compiles)
First Jetty Itests:
|
A bit better with Jetty:
Jetty bundle needs to be fixed - Jetty 12 has completely different artifact set. |
All Jetty 12 integration tests work. I had to remove all CDI/JSF examples and tests though:
Now onto Tomcat and Undertow integration tests for Jakarta EE 10 - should be much easier than Jetty 12! |
All Undertow 2.3.x tests work. |
Pax Web 10 won't have dedicated Keycloak support: |
All Karaf tests work too! |
https://github.com/ops4j/org.ops4j.pax.web/commits/main-jakarta-2025/ contains working Pax Web 10.0.0-SNAPSHOT version! |
Related to osgi/osgi#499
Target runtimes (as of Nov 2022):Target runtimes (as of Jun 2023):Target runtimes (as of March 2025):
See:
The text was updated successfully, but these errors were encountered: