Skip to content
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

Open
karianna opened this issue Jul 7, 2021 · 10 comments
Open

javax --> jakartaee namespace transition - Ecosystem tracking #71

karianna opened this issue Jul 7, 2021 · 10 comments

Comments

@karianna
Copy link

karianna commented Jul 7, 2021

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

  • Application Servers
  • Web Servers
  • MicroProfile implementers
  • IDEs
  • Frameworks
  • Monitoring tools
  • Testing tools
  • Porting tools
  • Cloud Providers

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+

@karianna
Copy link
Author

karianna commented Jul 7, 2021

The attached PDF gives some context when we were looking at this challenge in the Jakarta EE 9 time frame

JakartaEE-9-Tools-Vendor-Datasheet-2020-07-17-final (1).pdf

@keilw
Copy link
Member

keilw commented Jul 7, 2021

On the IDE side it would certainly be interesting to see, if Web Tools could have something to offer here.

@jeanouii
Copy link

jeanouii commented Jul 8, 2021

Saw on twitter that IntelliJ now has support for Jakarta and even some ways to convert and application to the new namespace

@karianna
Copy link
Author

karianna commented Jul 8, 2021

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!

@ehsavoie
Copy link

ehsavoie commented Jul 8, 2021

Maybe you should also add middleware tools like messaging brokers, transaction engines, ...

@karianna
Copy link
Author

karianna commented Jul 8, 2021

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!

@hantsy
Copy link

hantsy commented Jan 4, 2022

How about the Jdbc spec, I found in Jakarta EE 9 it is still using javax, and some APIs existed in the lagacy JDK. Not update in future ?

@karianna
Copy link
Author

karianna commented Jan 4, 2022

How about the Jdbc spec, I found in Jakarta EE 9 it is still using javax, and some APIs existed in the lagacy JDK. Not update in future ?

The move will be made in JakartaEE 10

@anbusampath
Copy link

How about the Jdbc spec, I found in Jakarta EE 9 it is still using javax, and some APIs existed in the lagacy JDK. Not update in future ?

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?

@hantsy
Copy link

hantsy commented Jan 5, 2022

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants