-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Upgrade to Jakarta EE #624
Comments
I may submit a pull request for this one, but would like first to clarify the strategy for getting there among the two described above. Since Pippo 1.x supports |
I agree. |
Working on it and I'm almost done, but have one question. Due to the changes in the way Jetty handles WebSockets, I need an access to Jetty What would be the best was to access it from there? Provided |
Here's my work so far: https://github.com/gkresic/pippo/tree/jakarta Notice hardcoded server access in Tests confirm that WebSocket endpoints are working. Unrelated, notice that my initial assumptions about servlet versions were incorrect: servlet specs 4 and 5 are the same, only difference being |
@gkresic When you have something functional please create a PR fore review and comments. It's more easy to compare the impact of the changes using the diffs view. |
Created WIP PR #639 |
This is an extension to #490 (first half of it, anyway). Over there it was proposed to to upgrade to servlet 4 spec, but nothing is said on javax -> jakarta namespace migration that is part of spec 4.
So I propose migration in 2 steps:
io.undertow:undertow-servlet-jakartaee9
dependencyIf Pippo doesn't have to support parallel versions for JavaEE and JakartaEE, then those two steps could be squashed into one and leave JavaEE compatibility behind.
Depends on #613
The text was updated successfully, but these errors were encountered: