Hi,
The Jersey supplied message body readers throw WebApplicationException
which then thrown causes the client side to throw a null pointer
exception when the jersey-server module is not present. This is
because a Response.ResponseBuilder implementation does not exist.
I think the right solution is for such readers to throw a
MessageBodyReaderException runtime exception which is then mapped on
the server side to a 400 client error response. Thus such an exception
on the client sid makes sense to the developer rather than reusing
WebApplicationException with dummy-based response builder.
This should apply to all the readers in core, atom, multipart etc that
are capable of detecting client errors.
What do others think?
Paul.