FIX - Jaxb configuration changed to serialize EntityUniquenessExceptionInfo #3943
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.
Brief description of the PR.
Before this PR Jaxb was not correctly serializing the EntityUniquenessExceptionInfo that we insert in the response body if needed. It was, instead, serializing to a basic ExceptionInfo without the additional fields in EntityUniquenessExceptionInfo class.
Description of the solution adopted
The problem was that the EntityUniquenessExceptionInfo class was not inserted inside the configuration of jaxb so the framework was not able to perform the operation