users@cxf.apache.org
Subject: Re: Fault thrown in Rest In-Interceptor not handled by ExceptionMapper
Thanks all. CustomOutFaultInterceptor + ResponseHandler handles all
use cases nicely for me. But, I notice the incoming Message to both is
missing most properties. In particular, QUERY_STRING is not set. I
gt;>>
>>>>
>>>>
>>>>
>>>> And my interceptor looks like:
>>>>
>>>> public class MyInterceptor extends AbstractPhaseInterceptor {
>>>> public FormatSettingInterceptor() {
>>>> super(Pha
ks like:
>>>
>>> public class MyInterceptor extends AbstractPhaseInterceptor {
>>> public FormatSettingInterceptor() {
>>> super(Phase.PRE_STREAM);
>>> }
>>>
>>> @Override
>>> public void h
gt;>>
>>> public class MyInterceptor extends AbstractPhaseInterceptor {
>>> public FormatSettingInterceptor() {
>>> super(Phase.PRE_STREAM);
>>> }
>>>
>>> @Override
>>> public void handle
filter and override a Response returned by the default mapper
Sergey
-Original Message-
From: Mike O'Neil [mailto:mton...@gmail.com]
Sent: 17 December 2009 21:12
To: users@cxf.apache.org
Subject: Re: Fault thrown in Rest In-Interceptor not handled by ExceptionMapper
Thanks for
PRE_STREAM);
>> }
>>
>> @Override
>> public void handleMessage(Message message) throws Fault {
>> throw new Fault("Not handled by ExceptionMapper!");
>> }
>> }
>>
>> Any insight or help would be appreciated.
>>
>> Much thanks,
>> Mike
>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/Fault-thrown-in-Rest-In-Interceptor-not-handled-by-ExceptionMapper-tp26833555p26834406.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
uot;Not handled by ExceptionMapper!");
> }
> }
>
> Any insight or help would be appreciated.
>
> Much thanks,
> Mike
>
>
--
View this message in context:
http://old.nabble.com/Fault-thrown-in-Rest-In-Interceptor-not-handled-by-ExceptionMapper-tp26833555p26834406.html
Sent from the cxf-user mailing list archive at Nabble.com.
I have an ExceptionMapper which handles exceptions from my Rest
service just fine. However when my "In" Interceptor throws a Fault,
the ExceptionMapper does not handle it. Instead I get the standard
(ugly) XML, e.g.:
error
message
Is that the expected behavior? My server is set up like: