On Jan 30, 2012, at 5:48 PM, Sergey Beryozkin wrote:
>> MethodNotAllowedException
>> BadRequestException
>> NotAcceptableException
>> InternalServerErrorException
>> UnauthorizedException
>> UnsupportedMediaTypeException
>> NotFoundException
>>
>>
>> Finally, these above exceptions would be useful on the server side.
>> *NOT* for application code to catch, but rather to write
>> ExceptionMappers for. So, Jersey/Resteasy whoever would throw those
>> exceptions internally, and applications could write ExceptionMapper for
>> those exceptions.
>>
>> Resteasy implemented these features on client/server after suggestions
>> from users.
I'm not sure I follow this. So the framework throws and catches the exception in order to call the user-defined mapper? Can you elaborate? This seems odd …
-- Santiago