Enthuware

Why the order is Client SH / Client LH in INBOUND message?

In inbound message the order of handlers is inversed not?

On an inbound message the SOAPHandlers run before the LogicalHandlers.

The order of the SOAPHandlers is reversed on an incoming message if you have configured more than one SOAPHandler. (but SOAPHandlers still run before the LogicalHandlers.)

The order of the LogicalHandlers is reversed on an incoming message if you have configured more than one LogicalHandler.

Regards,
Frits

I understand the answer and, i think, the explanation.
But, if by assumption had been SERVER LH's handleMessage() a return false I would have expected:
Client LH(O)- Client SH(O)- Server SH(I)- SERVER LH(I) - Client SH(I) - Client LH(I)

instead i had :
Client LH(O)- Client SH(O)- Server SH(I)- SERVER LH(I) - SERVER SH (O) - Client SH(I) - Client LH(I)

i don't understand well?

The sequence is reversed immediately.

Just write the events down like a request-response sequence:
If the problem occurs in Server SH the following will happen: If the problem occurs in Server LH the following will happen: Does this make it clearer?

Regards
Frits

Ok, i just understand

Hi,

Just to confirm so I understand this:

Suppose configuration file is as follows:

1) SH1
2) SH2
3) LH1
4) LH2

Then would the outbound handler chain ordering be as follows?

LH1, LH2, SH1, SH2

And inbound be

SH2, SH1, LH2, LH1 ?

I make this assumption based on section 9.2.1.2 Handler Ordering of JAX-WS 2.2 docs: "all logical handlers precede all protocol handlers".

Could you please confirm if I am correct with this assumption?

Thanks,
Victor.

Hi Victor,

Yes, you are correct!

Regards,
Frits

fjwalraven wrote:Hi Victor,

Yes, you are correct!

Regards,
Frits

Thanks.