Source: dzone.com
Jackson, JSON and the Proper Handling of Unknown Fields in APIs
by Imagine the following scenario: You have an application that integrates with another through the consumption of REST endpoints.
To paraphrase, and correct myself: whenever there is a property in JSON that has not been mapped to its java / DTO object, Jackson will throw this exception, *unless you tell Jackson that he can ignore such attributes*.
Setting up the object mapper will tell Jackson to ignore unknown attributes in all deserializations where that object mapper is used.
The JSON below will be used, which has the age attribute that is not known by the DTO.
To paraphrase, and correct myself: whenever there is a property in JSON that has not been mapped to its java / DTO object, Jackson will throw this exception, *unless you tell Jackson that he can ignore such attributes*.
Setting up the object mapper will tell Jackson to ignore unknown attributes in all deserializations where that object mapper is used.
The JSON below will be used, which has the age attribute that is not known by the DTO.
Related Articles
Community Partners
DevOps Careers