My fault, sorry about wasting your time.
I've checked the source, the exceptions escaped from the cxf
interceptors can be properly mapped only in 3.0.0-milestone2 due to be
release very shortly.
Can you try a trunk snapshot please just to double check ?
I'm wondering though why you are not seeing it working in
3.0.0.milestone1, hmm, the miliestone2 does test this scenario and so
3.0.0.milestone1 though the fix in m1 is temporary.
Have a look at
http://svn.apache.org/repos/asf/cxf/tags/cxf-3.0.0-milestone1/rt/frontend/jaxrs/src/main/java/org/apache/cxf/jaxrs/interceptor/JAXRSInInterceptor.java,
handleFault()
I'm not sure why it does not work given PRE_LOGICAL is after UNMARSHALL
which is where JAXRSInInterceptor sits.
Please download m1 source and debug if you are interested, as I said it
absolutely must work in m2
Sergey
On 22/01/14 10:32, nikosdim wrote:
I also changed my xml file
I deleted the
<cxf:bus>
<cxf:inInterceptors>
<ref bean="MyLoginInInterceptor" />
</cxf:inInterceptors>
<cxf:outInterceptors>
<ref bean="MyLoginOutInterceptor" />
</cxf:outInterceptors>
</cxf:bus>
and added this under the <jaxrs:server> tag
<jaxrs:inInterceptors>
<ref bean="MyLoginInInterceptor" />
</jaxrs:inInterceptors>
<jaxrs:outInterceptors>
<ref bean="MyLoginOutInterceptor" />
</jaxrs:outInterceptors>
but still the same problem. My exception mapper is never invoked and
WebApplicationException is thrown as normal.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Custom-Response-from-handleFault-JAX-RS-tp5738651p5738955.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
