Hi Gabo
I've updated one of the tests to show that an exception mapper can report a text/plain message and no Result tags are added. Have a
look please at [1]
here's the trace :
*****************************
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain
Content-Length: 28
Server: Jetty(6.1.11)
No book found at all : 12345
*****************************
> Is it possible to specify a custom provider from an ExceptionMapper
implementation
No, ExceptionMapper is a provider itself
I was hoping to avoid the chain-abort work-around.
I thought you removed the chain-abort work-around ?
I'm sorry if I'm missing something. Obviously, those gremlin <Result> tags are added somewhere, but I just don't see at the moment
where. Is there any chance you can debug the code a bit, starting from JAXRSOutInterceptor ?
Thanks, Sergey
[1]
https://svn.apache.org/repos/asf/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/jaxrs/BookExceptionMapper.java
----- Original Message -----
From: "Gabo Manuel" <[email protected]>
To: <[email protected]>
Sent: Wednesday, February 18, 2009 5:20 AM
Subject: Re: [JAX-RS] Fault handling
Hi Sergey,
Is it possible to specify a custom provider from an ExceptionMapper implementation? Or maybe a work around to remove the tags? I
was hoping to avoid the chain-abort work-around.
Again, my thanks.
Gabo
Sergey Beryozkin wrote:
Hi Gabo
Many thanks for creating the JIRAs.
ExceptionMappers are not CXF interceptors, they can be categorized as
JAXRS providers only. I'm still unclear at all as to where such Result
tags may come from - needs to be investigated indeed. It looks like
text_plain responses are wrapped ?
Cheers, Sergey
