Allow customizing 'alias to bean' property not found behavior #2287
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.
Scenario
A developer updates a stored procedure to return an additional column; this is generally expected to be a safe change.
The default behavior of
AliasToBeanResultTransformer
is to throw an exception when a value is observed but there is no field/property on the target instance to accept the value.This change retains the existing behavior, but allows for specialization.
Here was the temporary workaround that I came up with which can be greatly simplified.
Before
After