Hi toshi, thanks for that detailed answer. If I understood you right it is like this: if I want to stop the chain and return with an error message to the client, this is not possible with the axis-implementation?! So probably I will just set a session-parameter in my handler, that I have to look for in called methods. Thats suboptimal, but I do not have to much time :-( And if I want to use that JAX-rpc, how do I do? All I do at the moment is, just deploying the handler in the wsdd, but without a hint to axis-impl. Where would I have to define to use jax-rpc? inside the java-code of the handler?
And waht about my problem with the throwing of axis-faults. Even with try catch everywhere on the client side, the stacktrace is printed if the axis-fault is thrown by a handler. is it normal? thanks in advance and Greetings from Hamburg/Germany Seppo -----Ursprüngliche Nachricht----- Von: Toshiyuki Kimura [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 19. Dezember 2002 05:01 An: [EMAIL PROTECTED] Betreff: Re: Stopping the process of invocation by a Handler Hello Sebastian, > how can stop the process of invocation with the help of a handler? As you may know, AXIS has two implementations of "handler"; AXIS and JAX-RPC. The easiest way what you want to do is JAX-RPC imp., I think. Because the JAX-RPC ver 1.0 specifies the sequence of HandlerChain (includes stopping the HandlerChain and the target service endpoint). But, please note that the current version of AXIS (1.1 Beta) has a bug related the way of using above. I've already posted it to Bugzilla (the Apache bug database). You can refer the detail of the bug at the following site: <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15478> I hope this helps you. Best Regards, Toshiyuki Kimura <[EMAIL PROTECTED]> R&D Headquaters NTT DATA Corporation
