-
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):
|
Changes between 5 and 6 (interfaces):
Changes between 5 and 6 (documentation):
Changes between 5 and 6 (implementation):
Changes between 5 and 6 (other):
|
…o be verified later. for now it just compiles)
Another problem with Jetty 12 is the use of
or
Similar problem is described under spring-projects/spring-boot#7161 |
Are there any news on this? |
Well, at some point I created very crude implementation of pax-web-extender-whiteboard which implements https://docs.osgi.org/specification/osgi.cmpn/8.1.0/service.servlet.html and it worked with Jolokia 2. Last week Jetty 12.0.7 was released and I was going to get back to this issue. Maybe next week I'll revisit it... |
Is there a way we can support jakarta. API development of this (especially for Tommcat). We would like to see it in Karaf. |
There is a way, but unfortunately it's a long way. while other JakartaEE implementations are ready, their OSGi support is far from perfect... And the branch https://github.com/ops4j/org.ops4j.pax.web/commits/main-jakarta/ is open for PRs, so if anyone could contribute, it'd be great ;) |
Related to osgi/osgi#499
Target runtimes (as of Nov 2022):Target runtimes (as of Jun 2023):
See:
The text was updated successfully, but these errors were encountered: