HHH-19529 Check bytecode generated classes with stable names class loaders to ensure EE subdeployment contained entity classes are used in preference to top level deployment (e.g. EAR/lib) #10305
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…aders to ensure EE subdeployment contained entity classes are used in preference to top level deployment (e.g. EAR/lib) Signed-off-by: Scott Marlow <[email protected]>
|
The Jakarta EE 10 Platform TCK tests pass with this change. |
mbellade
approved these changes
Jun 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Address https://hibernate.atlassian.net/browse/HHH-19529 + https://issues.redhat.com/browse/WFLY-20572
Ensure that bytecode generated proxies are generated in the referenceClass class loader to ensure EE subdeployment (e.g. war) contained entity classes are used in preference to top level deployment (e.g. EAR/lib).
More specifically, if an application EAR contains the entity classes in the ear/lib and also has several WARs that also contain the same entity classes, the war copy of the entity classes should be used. There may also be some WARs that do not contain those entity classes so those WARs should use the entity classes contained in the EAR/lib.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.