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
about your question:
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
Harald Pollak wrote:
A jax-rpc handler chain can only handle jax-rpc handlers but axis can
deal with both
That's true.
and jax-rpc handler are allways global and not service spezific.
That's not true. JAX-RPC handlers are service specific in Axis.
Thus, I am wondering why they are invoked
ok!
I agree with you in all points.
1. Its realy confusing that client and server chain are different.
2. If jax-rpx handlers are service spezific ( I have missunderstood somthing )- the client should
allso act like the server.
So I allso think its a bug.
Harry
Am Do, den 11.12.2003
Axis developers: was the decribed behaviour intentionally coded like this
or is it a bug?
Harald Pollak wrote:
ok!
I agree with you in all points.
1. Its realy confusing that client and server chain are different.
2. If jax-rpx handlers are service spezific ( I have missunderstood
somthing
Hi Thilo!
In the Axis Architecture Guide
(http://ws.apache.org/axis/java/architecture-guide.html) the behaviour
you describe is explained to be intended.
(Beside points 3 and 7, which are not explained).
Imho the figures show very well, why there's a different order of chains
on server and
Hi!
You're right - the figures show very well why there are different orders
on the client and the server for system-specific, global and transport-
specific chains. But that wasn't the question :-)
The question was about what's not explained in the figures: why are the
JAX-RPC handlers invoked
