Problem with JsonType serialization with spring-data 3.2 and hibernate 6.3 #704
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.
I ran into this issue while migrating my app from spring boot 2 to spring boot 3. This PR contains a test case to illustrate the problem.
There are some Entity objects with Java collection type members that map to json column in a table. They are annotated with JsonType. I noticed the tests for persisting those entities using named query were failing after migrating to spring boot 3. It looks like the code path in hibernate for handling named query is completely different from code path for persisting. It ends up doing Java serialization instead of the custom serialization for JsonType.