Poor jackson parsing error message in MappingJackson2HttpMessageConverter [SPR-11603] #16226
Hi all, while struggling with serialization bugs I've noticed that the debugging for SerializationContext.hasValueDeserializerFor
is pretty bad if called by the ObjectMapper.canDeserialize method, that just pass null on the cause parameter
and MappingJackson2HttpMessageConverter does exactly that
It is possible to improve this bubbling in some way the exceptions from the canDeserialize method?
Affects: 4.0 GA
The text was updated successfully, but these errors were encountered:
Juergen Hoeller commented
Looks like you were using 4.0 GA there, not 4.0.2... Since as of 4.0.1 and with a refined version in 4.0.2, we are passing an exception holder to Jackson, logging a resulting cause if exposed to us. You need to use a minimum of Jackson 2.3 and have your warn log level activated, then you should start seeing corresponding log entries.
As a consequence, I'm resolving this as fixed in 4.0.2 for the time being. Please reopen if anything is missing there.