On Tuesday 01 June 2010 11:21:46 am Glen Mazza wrote: > When exceptions occur, the interceptor chain is processed in reverse > direction (same with JAX-WS handlers). You'll need to do your error > handling towards the beginning of the service-side interceptor chain, not > at the end of it.
Well, the other thing thing to do would be to add an interceptor at the start of the server side "FaultOut" chain that would take the fault in the message and do whatever needs to be done to it. That's probably the preferred route as the interceptor would only get called for the faults. Dan > HTH, > Glen > > sur04sep wrote: > > Hi, > > I need to send custom error codes for all kind of exceptions(even run > > time exception). > > For this I wrote a OutInterceptor extending AbstractSoapInterceptor with > > super(Phase.MARSHAL) constructor. > > But control is not going to this interceptor in case of any run time > > exception. Only in case of successful processing control is coming to > > this interceptor. > > I have overridden both handleMessage and handleFault methods. > > What I could be doing wrong? > > And what is the correct approach to handle exception? > > > > Regards, > > seshu -- Daniel Kulp [email protected] http://dankulp.com/blog
