-
Notifications
You must be signed in to change notification settings - Fork 9
-
Notifications
You must be signed in to change notification settings - Fork 9
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
javax --> jakartaee namespace transition - Ecosystem tracking #71
Comments
The attached PDF gives some context when we were looking at this challenge in the Jakarta EE 9 time frame |
On the IDE side it would certainly be interesting to see, if Web Tools could have something to offer here. |
Saw on twitter that IntelliJ now has support for Jakarta and even some ways to convert and application to the new namespace |
Updated the sheet thank you! |
Maybe you should also add middleware tools like messaging brokers, transaction engines, ... |
Added a section but haven't really populated it yet, any help is much appreciated! |
How about the Jdbc spec, I found in Jakarta EE 9 it is still using |
The move will be made in JakartaEE 10 |
I thought jdbc is part of JDK itself, never part of Java EE or Jakarta EE. Just curious to know that am I missing anything? |
@anbusampath I remember the Jdbc APIs in JDK does not include XA Resources and just design for desktop/client applications. Jdk is modularized, not sure the future of jdbc module. |
This issue is the umbrella issue for setting up a tracking system to track the javax to jakarta namespace changes in the ecosystem (popular libraries, frameworks, tools, servers, etc).
--> Please feel free to edit The Tracking Sheet <--
Plan for enabling javax -> jakarta adoption by ecosystem
Highlight compatibility success stories (e.g. Eclipse Transformer, application migrations)
Evaluate compatibility options, e.g. “legacy” profile, or “MP” profile
Monitor/measure progress for tools targeted for supporting Jakarta EE 9+
The text was updated successfully, but these errors were encountered: