You could make use of Jackson’s Mix-Ins feature, coupled with the Creator feature. The Mix-Ins feature alleviates the need to annotate the original third-party code, and the Creator feature provides a mechanism for custom instance creation. For yet more customization, it’s not too involved to write a custom deserializer.
So it turned out that, the value of request body is not passed in because I need to have the @RequestBody annotation not only in my interface, but in the actual method implementation. Once I have that, the problem is solved.
In this case you need to annotate the relationships with @JsonManagedReference and @JsonBackReference like this: @ManyToOne @JoinColumn(name = “company_id”, referencedColumnName = “id”) @JsonBackReference private Company company And @OneToMany(mappedBy=”company”) @JsonManagedReference private Set<Employee> employee = new HashSet<Employee>(); There is a nice example here
Support for Jackson 2.7 will be added in Spring 4.3. See https://jira.spring.io/browse/SPR-13483. For now you aren’t able to use it without providing your own integration classes.
This issue is solved! Follow this Add support for Jackson serialization views Spring MVC now supports Jackon’s serialization views for rendering different subsets of the same POJO from different controller methods (e.g. detailed page vs summary view). Issue: SPR-7156 This is the SPR-7156. Status: Resolved Description Jackson’s JSONView annotation allows the developer to control which … Read more
What you want in the Child class is not @JsonProperty but instead @JsonIgnore(false).
You can mark a property as required with the @JsonProperty(required = true) annotation, and it will throw a JsonMappingException during deserialization if the property is missing or null. Edit: I received a downvote for this without comment. I’d love to know why, since it does exactly the right thing.
Use this solution, it is more effective and modern than my solution: https://stackoverflow.com/a/45456037/4886918 Thanks @Benjamin Lucidarme. I resolved my problem using: @Temporal(TemporalType.DATE) @JsonFormat(shape = JsonFormat.Shape.STRING, pattern = “dd/MM/yyyy”, locale = “pt-BR”, timezone = “Brazil/East”) private Date birthDate; I changed timezone to “Brazil/East” or “America/Sao_Paulo” and working now Thanks
If you use json validator, you can see more detailed error message: Parse error on line 6: …ntry”, }, { “id ———————^ Expecting ‘STRING’ you have extra comma there after “xx-xx-xxxx,x – street, x – country”. If you remove it from both two places, you have valid JSON and Jackson parsing works.
Use the WebMvcConfigurer.configureMessageConverters() method: Configure the HttpMessageConverters to use […] If no message converters are added to the list, default converters are added instead. With @Configuration you have: @Configuration class MvcConf extends WebMvcConfigurationSupport { protected void configureMessageConverters(List<HttpMessageConverter<?>> converters) { converters.add(converter()); addDefaultHttpMessageConverters(converters); } @Bean MappingJacksonHttpMessageConverter converter() { MappingJacksonHttpMessageConverter converter = new MappingJacksonHttpMessageConverter() //do your customizations here… … Read more