Thanks for the response Ricky. I haven't tried throwing an exception, but i guess then it would go into handleFault not handleResponse. I have looked at your earlier posting "Handler Chain Limitations". According to jax-rpc spec handlers return boolean response to chain invoker indicating the success or failure of handler invocation unlike the AXIS implementation where it is void invoke(..) and the only way to get output from invoke is to throw exception. Does this mean that AXIS doesn't follow JAX-RPC spec on handler chains? I have a situation where i have to stick to jax-rpc interfaces and jax-rpc does provide control over handler chain flow which is an elegant way of handling the scenario instead of throwing an exception
Regards, Sreekant Ricky Ho wrote: > Few months ago, I run into the same issue when I try to implement a cache > handler. The answer I got back from Steve is the only way to stop the > handler passing on the request is to throw an exception, in that case a > SOAP Fault is send back to client. > > I guess this behavior is still the same now. > > Rgds, Ricky > > At 10:40 AM 2/21/2003 -0500, Sreekant Thirunagari wrote: > >Hi all, > > I started studying axis recently and have done some work on it. I > >am having problems with handler chain management. According to my > >understanding of the jax-rpc spec we can block the handler chain flow at > > > >any point and return from that point provided that the appropriate > >SoapMessageContext is provided. The runtime system should be responsible > > > >for invoking the response handlers. > > My problem is i have a chain of handlers and i need to block the > >request flow at runtime on certain conditions evaluated in handleRequest > > > >method. Correct me if i am wrong.. according to my understanding if you > >return a false from handleRequest request handler chain is blocked and > >target service endpoint should not be invoked.. and response handler > >chain should start processing (should it start from the same handler > >that returned false???). I see that axis does return from request > >handler chain but it still invokes the target service endpoint and > >starts the response chain as configured. Can any one please explain me > >is this the expected behaviour, did i miss anything or is it a problem > >with axis handler chain implementation. > > > >Regards, > >Sreekant
