-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE deserializing collection with @JsonCreator
and ACCEPT_CASE_INSENSITIVE_PROPERTIES
when JSON and Java property names match
#1854
Comments
Ok at this point I will need a simplified version to remove all unrelated aspects (client, server framework). Interestingly enough, 3.0.0-SNAPSHOT does not fail, so something in handling has been improved. |
Added simplified stand-alone test which reproduces the problem. |
Quick note on work-around: I haven't quite figured out why assignment of value deserializer fails, at low level, but it is due to mismatch of property names (before being unified).
by either adding name match ( |
@JsonCreator
and ACCEPT_CASE_INSENSITIVE_PROPERTIES
when JSON and Java property names match
Looks like there was a conflict in Unfortunately at this point I think I will only backport the fix to |
Thank you! |
Attempting to deserialize JSON fails when the following conditions are met:
ObjectMapper
hasMapperFeature.ACCEPT_CASE_INSENSITIVE_PROPERTIES
enabled.@JsonCreator
on constructor or factory method@JsonProperty
name is identical to the Java POJO property nameStack trace:
Sample maven project attached. Runs unit test against a Feign client with JacksonDecoder.
Vary the Jackson version to 2.8.7 or below and it passes.
Disable
ACCEPT_CASE_INSENSITIVE_PROPERTIES
and it passes.Use getters instead of
@JsonCreator
and it passes.jackson-test.zip
The text was updated successfully, but these errors were encountered: