Skip to content

Clarify deployment transformer behavior and disable flag #709

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.

Sign up for GitHub

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

Open
Elifzeynepedman wants to merge 3 commits into
base: main-6
Choose a base branch
from
Open

Clarify deployment transformer behavior and disable flag #709

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
049258d
Clarify deployment transformer behavior and disable flag
Elifzeynepedman Jan 28, 2026
401ef68
additonal fixes
Elifzeynepedman Jan 30, 2026
2133fa9
additonal fixes 2
Elifzeynepedman Jan 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions enterprise/docs/modules/ROOT/pages/General Info/Jakarta EE 8 Support.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,11 @@ In most cases this means that users that are migrating their applications from a

Fortunately, Payara Enterprise distributions (_Server_ and _Micro_, explicitly) include a *Deployment Transformer* tool that automatically executes the conversion of a Jakarta EE 8 application's components using at deployment time, allowing users to have their Jakarta EE 8 applications transformed on the fly into the Jakarta EE 10 namespace.

NOTE: The deployment transformer is enabled by default on both Payara Platform distributions.
NOTE: The deployment transformer is enabled by default on Payara Enterprise.

Users can disable the deployment transformer by setting the `fish.payara.deployment.transform.namespace` system property to `false` and restart the corresponding server instances. This might be desired if users have no intention on deploying Jakarta EE 8 applications and want to spare the extra overhead of the deployment transformer scanning their applications in vain.
Because the deployment transformer operates at the archive level, it may repackage application archives and nested JARs as part of the transformation process. This can result in metadata such as `META-INF/MANIFEST.MF` being regenerated, which may invalidate existing cryptographic signatures on vendor-signed JARs included in the application (for example, resource adapters or security providers).

Users can disable the deployment transformer by running the command `asadmin create-system-properties fish.payara.deployment.transform.namespace=false` and restart the corresponding server instances. This might be desired if users have no intention on deploying Jakarta EE 8 applications and want to spare the extra overhead of the deployment transformer scanning their applications in vain.

IMPORTANT: The deployment transformer will allow most Jakarta EE 8 applications to run on a Payara Platform 6 distribution with no changes, however, in some cases user intervention will be required to fix breaking changes introduced in Jakarta EE 10 (like pruned APIs, for example).

Expand Down