As I have understood your and Dapeng Wang presentations on W-JAX:
A jax-rpc handler chain can only handle jax-rpc handlers but axis can deal with both, and jax-rpc handler are allways global and not service spezific.
so the transport handlers und global handlers build the start and end point from the jax-rpc chain ( all things dealing with jax-rpc handlers can be done ) beginning with the global handler section the chain continue with axis handlers and all pissibilities from this handlers.
best regards
Harry
Am Do, den 11.12.2003 schrieb Thilo Frotscher um 13:44:
Hi! Browsing the source code of Axis 1.2 alpha I found out, that the order in which handlers are called on the client side is as follows: 1) Service Specific Request Chain 2) Global Request Chain 3) JAX-RPC Handlers 4) Transport Specific Request Chain 5) Send SOAP message to service 6) Transport Specific Response Chain 7) JAX-RPC Handlers 8) Global Response Chain 9) Service specific Response Chain Question: why are JAX-RPC handlers called between global chain and transport specific chain? Shouldn't they be called between service specific chain and global chain? After all, the JAX-RPC-handler chain is service specific and therefore configures inside a service configuration. On the server side, the order is like I would have expected it: 1) Transport Specific Request Chain 2) Global Request Chain 3) JAX-RPC Handlers 4) Service Specific Request Chain 5) invoke web service 6) Service specific Response Chain 7) JAX-RPC Handlers 8) Global Response Chain 9) Transport Specific Response Chain Is the behaviour on the client a bug? Thanks, Thilo
