Leniently resolve entities during property path traversal - #3517
Open
mp911de wants to merge 3 commits into
Open
Conversation
We now rely on MappingContext.getPersistentEntity(…) for persistent entity resolution instead of validating PersistentProperty.isEntity(…) ourselves. isEntity considers key and value types when using Map types whereas getPersistentEntity(…) only considers the value type for property path traversal. This difference in behavior caused MappingException during property path traversal amplified by eager auditing metadata resolution. Additionally, we leniently resolve a backing persistent entity when obtaining property paths from a collection or map type as MappingContext contains registrations for Map-based entity types that resolve to a raw Map type erasing type parameters.
Fix Javadoc to reflect API behavior.
mp911de
force-pushed
the
main
branch
3 times, most recently
from
August 4, 2026 14:39
bde036c to
adb1c6d
Compare
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
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.
We now rely on
MappingContext.getPersistentEntity(…)for persistent entity resolution instead of validating PersistentProperty.isEntity(…) ourselves. isEntity considers key and value types when using Map types whereas getPersistentEntity(…) only considers the value type for property path traversal. This difference in behavior caused MappingException during property path traversal amplified by eager auditing metadata resolution.Additionally, we leniently resolve a backing persistent entity when obtaining property paths from a collection or map type as MappingContext contains registrations for Map-based entity types that resolve to a raw Map type erasing type parameters.
Closes #3515