BeanDeserializerBase (2.6.0 regression): only update creatorProps with CreatorPropertys #881
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.
It looks like the fix to issue [#795] introduced a bug as illustrated by the test case. An
ArrayStoreExceptionoccurs when attempting to assign anObjectIdReferencePropertyto thecreatorPropsarray, understandably. Others have mentioned this on a similar (but I believe un-related) issue here and here.Doing something like
Arrays.copyOf(...)when theCreatorPropertyarray is returned from the value instantiator here prevents theArrayStoreExceptionbut seems to cause downstream problems. Only updatingcreatorPropswith an actualCreatorPropertyseems reasonable to me but I am not super familiar with jackson internals.