-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.5.8.Final, 3.14.0.Final
-
None
-
-
Undefined
When using Resteasy with Jackson data mapping, deserializing input JSON data might result in databind exceptions such as com.fasterxml.jackson.databind.exc.InvalidFormatException. These might, for instance, appear of a client-provided UUID string representation is invalid. According to 27.2. Resteasy Built-in Internally-Thrown Exceptions such errors should be raised as ReaderException instances
All exceptions thrown from MessageBodyReaders are wrapped within this exception. If there is no ExceptionMapper for the wrapped exception or if the excepiton isn't a WebApplicationException, then resteasy will return a 400 code by default.
However, in this case the plain com.fasterxml.jackson.databind.exc.InvalidFormatException is raised and I would have to install a quite generic exception mapper to return a bad request in this case. That exception mapper could accidentally also cover exceptions generated elsewhere in the code.