On Wed November 18 2009 2:11:55 pm vickatvuuch wrote: > 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?
Probably call chain.getIterator(), iterate through to find the one that is instanceof WebFaultOutInterceptor, then call chain.remove(..) with it. Dan > > 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 [email protected] http://www.dankulp.com/blog
