Add support for collecting multiple deserialization failures during processing, not just first one (original) (raw)

Currently, deserialization fails as soon as a property of a class can not be deserialized properly. In case a source JSON document contains multiple errors, this will usually cause the sender to be notified of the first error, it will then retry, and run into the second error.

It would be cool if there was a Jackson mode that collects the exceptions that occur on deserialization and report a compound exception eventually to contain all the problems found so that a more exhaustive report about which fields could not be deserialized can be sent to clients.