Hi Glen;
I know we can put MessageReciver as last handler of some phase , but what if
some one add a phase after that phase. Any way there is a solution for that
as well , by putting constraint saying that MessageReciver phase is the last
phase of the chain and no one can change that , as well as TransportOutPhase
is the last phase and that also can not be changed . What do you think about
that approach. I also like the idea of one chain rather invoke something and
come back and invoke message receiver.
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Glen Daniels" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, December 20, 2005 7:15 PM
Subject: Re: [Axis2] Possible bug in the AxisEngine.resume() method
Hi Deepal:
Deepal Jayasinghe wrote:
Hi Chamikara;
I am not sure I am giving the right answer, any way the reason behind
treating Message reciver seperately is the following
say that you add message receiver as the end of the operation chain
and you just call msgCnx.invoke(); , what if some one change the
handler chain at the runtime to add a handler after the message
receiver. To avoid that kind of scenario we treat Message Receiver
separately.
Isn't that easily solved by just having the MessageReceiver be set as the
last handler?
--Glen
