Validation
Every value is checked with Bean Validation before it is set. All violations of one call come back together, each with its path.
Annotations on the model
The mapper calls validateValue for each property with the value from the JSON. A value that violates a constraint is not set.
One exception with every violation
After the whole graph was visited, the mapper throws ErrorRequestException if anything was rejected: a Bean Validation violation, a wrong JSON kind, a number out of range, an unknown enum constant, an unreadable date or an unresolved reference. Each ErrorRequest carries a path through the graph, collection indexes included, and the constraint's message.
ErrorRequest is itself annotated for JSON, so a REST endpoint can serialize the list as its error response.
Valid values are already set
Validation runs per property. When the exception is thrown, the valid properties of the same call have been written already.
The mapper first reads, resolves and validates the whole document and writes only when it is valid. A rejected request leaves the object as it was; ErrorRequestException is an IllegalArgumentException.