The namespace rename from javax. to jakarta. (done by recipes), and the API-level changes up to Jakarta EE 10 or 11. The advisors report what remains, and the AI agent fixes it.
Recommended Migration Sequence
The Azul Payara AI Upgrade Assistant changes the Jakarta EE API level of your application. Depending on your starting point, other steps are needed before and after it.
Order of Steps
| Step | Tool | What it handles |
|---|---|---|
1 |
Azul Payara AI Upgrade Assistant |
|
2 |
Payara Server upgrade |
Upgrade the server installation, domain configuration and deployed applications to a Payara Server version that supports your target Jakarta EE level. See the Payara Server Upgrade Tool. |
3 |
Test and deploy |
Run your own tests and deploy the upgraded application to the target server. The Azul Payara AI Upgrade Assistant compiles the application but never deploys it. |
Your Server Must Support the Target Jakarta EE Level
An application upgraded to a higher Jakarta EE level cannot be deployed on a server that does not support that level. The Azul Payara AI Upgrade Assistant compiles your application but never deploys it, so it cannot detect this for you.
|
Important
|
For example, an application upgraded to Jakarta EE 10 or 11 does not run on Payara Server 5. Upgrade the server to a version that supports your target Jakarta EE level. |
Taking Smaller Steps
If you cannot move to Jakarta EE 11 in a single step, upgrade in stages: first to Jakarta EE 10, deploy and test, then to Jakarta EE 11. Use -Dmigration.target=10 for the first stage. Commit between the stages, so you can review each step.
The move from Jakarta EE 8 to 9 is a namespace change only and is done by recipes, without the AI agent. It is the lowest-risk step out of javax.*.