Dan, I was thinking of making a custom WebFaultOutInterceptor and inserting it before the default one in the PRE_PROTOCOL phase. Could you tell me how to remove the default WebFaultOutInterceptor from the chain?
Thanks, -Vitaly dkulp wrote: > > > One way of achieving this is to stick an interceptor very early in the > FaultOut chain that would get the chain from the message and manipulate > the > chain. Adding your own interceptors if needed, removing those you don't > want, etc... The chains are completely modifiable at run time during > execution. > > Dan > > > On Wed November 18 2009 11:37:28 am vickatvuuch wrote: >> Hi ! >> I'm trying to figure out how to pickup all exceptions (including >> IllegalArgument, NPE, etc) >> that may be thrown from custom IN interceptors as well as Port Impls such >> that I would be able to wrap it up in MyWebFault which has defined >> ERROR_CODEs exposed through WSDL. >> I see that there are several OUT interceptors processing exceptions, my >> question is how to replace >> default one with my custom version of it or should I insert mine in front >> of them and pre-process the message instead? The approach should also >> work >> with REST and hopefully be in once place. >> >> Thanks, >> -Vitaly >> > > -- > Daniel Kulp > dk...@apache.org > http://www.dankulp.com/blog > > -- View this message in context: http://old.nabble.com/Soap-Fault-handling-in-the-Out-Interceptor-tp26408430p26413820.html Sent from the cxf-user mailing list archive at Nabble.com.
