Skip to content

Conversation

11rx4f
Copy link
Contributor

@11rx4f 11rx4f commented Jul 25, 2025

Follow-up: #323

@bjhargrave
Copy link
Contributor

Can you provide some context on these changes? They seem to be references to much older JavaEE versions.

@11rx4f
Copy link
Contributor Author

11rx4f commented Aug 28, 2025

These old schemas are used in javaee/tutorial-examples, which are featured in the Java EE Tutorial (https://javaee.github.io/tutorial/).

Since these are schemas used in source code officially guided by Java EE, it's highly probable that they are also being used in user environments.

Therefore, I believe they should be targeted for transformation.

@bjhargrave
Copy link
Contributor

The transformer Jakarta standard rules are for Jakarta 8 => Jakarta 9 transforms. From the old Jakarta 8 javax names to the Jakarta 9 jakarta names.

I don't think it is appropriate to also include renames from pre-Jakarta 8 things in these standard rules. There are probably many such name changes over the releases of Java EE.

But you can easily define your own rules for your specific work loads such as these.

@11rx4f
Copy link
Contributor Author

11rx4f commented Sep 10, 2025

I agree with the basic concept of Eclipse Transformer.

On the other hand, to introduce this tool to Japanese users who are particularly hesitant about migrating to Jakarta EE, I would like to use applications from javaee/tutorial-examples as examples (actually my colleague presented on this project as examples at JakartaOne 2025 Japan). My goal is to convert these applications completely so they run correctly with Jakarta EE 9 or later, utilizing Eclipse Transformer.

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

Successfully merging this pull request may close these issues.

2 participants