On 30/09/12 14:33, Benson Margulies wrote:
I've got a case, for which I'm about to file a JIRA, in which I think
that it's important that a particular situation leads to a log message
with some minimal content with a particular log level. Have we got any
tests for cases like this? I'm thinking
On Sun, Sep 30, 2012 at 12:59 PM, Sergey Beryozkin sberyoz...@gmail.com wrote:
On 30/09/12 14:33, Benson Margulies wrote:
I've got a case, for which I'm about to file a JIRA, in which I think
that it's important that a particular situation leads to a log message
with some minimal content with
Hi Benson
On 30/09/12 15:22, Benson Margulies wrote:
An exception mapper is for the entire service, not for a resource. And
it has no access to the @Produces of a resource, nor to request
headers. Doesn't this make it mighty difficult to be well-behaved?
You can inject @Context HttpHeaders and
Hi
On 30/09/12 18:03, Benson Margulies wrote:
On Sun, Sep 30, 2012 at 12:59 PM, Sergey Beryozkinsberyoz...@gmail.com wrote:
On 30/09/12 14:33, Benson Margulies wrote:
I've got a case, for which I'm about to file a JIRA, in which I think
that it's important that a particular situation leads
Also updated the mapper to optionally report an error message (can be
customized by extending the mapper) by setting an 'addMessageToResponse'
property - which is ignored if the exception already contains Response
with a non-null entity
Sergey
On 30/09/12 18:39, Sergey Beryozkin wrote:
Hi
