About Question enthuware.ocejws.v6.2.318 :

Moderators: Site Manager, fjwalraven

Post Reply
evefuji
Posts: 21
Joined: Fri Apr 11, 2014 8:57 pm
Contact:

About Question enthuware.ocejws.v6.2.318 :

Post by evefuji » Sat Jun 07, 2014 2:59 pm

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

In inbound message the order of handlers is inversed not?

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.318 :

Post by fjwalraven » Mon Jun 09, 2014 12:35 am

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

fabiolino
Posts: 25
Joined: Wed Jun 24, 2015 7:26 am
Contact:

Re: About Question enthuware.ocejws.v6.2.318 :

Post by fabiolino » Wed Jul 01, 2015 4:12 am

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 :o :
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?

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.318 :

Post by fjwalraven » Wed Jul 01, 2015 6:50 am

The sequence is reversed immediately.

Just write the events down like a request-response sequence:

Code: Select all

Client LH -> Client SH -> Server SH -> Server LH ----   (request)
                                                     | 
Client LH <- Client SH <- Server SH <- Server LH ----   (response)
If the problem occurs in Server SH the following will happen:

Code: Select all

Client LH -> Client SH -> Server SH 
Client LH <- Client SH <-  
If the problem occurs in Server LH the following will happen:

Code: Select all

Client LH -> Client SH -> Server SH -> Server LH
Client LH <- Client SH <- Server SH <- 
Does this make it clearer?

Regards
Frits

fabiolino
Posts: 25
Joined: Wed Jun 24, 2015 7:26 am
Contact:

Re: About Question enthuware.ocejws.v6.2.318 :

Post by fabiolino » Wed Jul 01, 2015 7:16 am

Ok, i just understand

victor2016
Posts: 12
Joined: Wed Jan 20, 2016 7:16 pm
Contact:

Re: About Question enthuware.ocejws.v6.2.318 :

Post by victor2016 » Sun Aug 07, 2016 2:25 pm

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.

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.318 :

Post by fjwalraven » Sun Aug 07, 2016 2:47 pm

Hi Victor,

Yes, you are correct!

Regards,
Frits

victor2016
Posts: 12
Joined: Wed Jan 20, 2016 7:16 pm
Contact:

Re: About Question enthuware.ocejws.v6.2.318 :

Post by victor2016 » Sun Aug 07, 2016 2:47 pm

fjwalraven wrote:Hi Victor,

Yes, you are correct!

Regards,
Frits
Thanks.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests