Sergey Beryozkin-5 wrote > That refers to the in fault interceptors and as I said they will not be > called on the server side, this is why the "outFaultInterceptors" > section as typed above has to be used...
outFaultInterceptors are not called on parsing exceptions. They are not even a part of the fault chain. It is clearly visible from the log I have provided. And here is why. 1) Factory ... hardcoded providers, not smart for a framework, It should be configurable, at least. Than in JAXRSInInterceptor exception is caught and pushed to a default WebApplicationExceptionMapper that has been statically configured on the factory ... So at the end there are no way to catch an exception as exception handling is hard coded. And even if I register my own ExceptionMapper on the SHARED_FACTORY the default one takes precedence ... see ExceptionMapperComparator class in org.apache.cxf.jaxrs.provider.ProviderFactory -- View this message in context: http://cxf.547215.n5.nabble.com/Intercepting-exceptions-on-the-server-side-tp5719964p5720037.html Sent from the cxf-user mailing list archive at Nabble.com.
