~Future is Open~
- Original Message -
From: Glen Daniels [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
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
-dev@ws.apache.org
Sent: Thursday, December 15, 2005 8:29
PM
Subject: Re: [Axis2] Possible bug in the
AxisEngine.resume() method
Hi Glen,Since TransportSender already extend the
Handler interface it can be easily attached to the end of the handler chain.
But MessageReceiver
Hi Chamikara:
+1 and -1 to parts of this patch. :)
First, I agree about merging the chains (op-specifc and global) into one
- that was the intent (a single EC) from the first Axis2 meetings. The
problem with doing it here is that I think this method might get called
before operation dispatching
Hi Glen,
Please see my comments below.On 12/15/05, Glen Daniels [EMAIL PROTECTED] wrote:
Hi Chamikara:+1 and -1 to parts of this patch. :)First, I agree about merging the chains (op-specifc and global) into one- that was the intent (a single EC) from the first Axis2 meetings.Theproblem with doing
Hi Chamikara!
Actually what I merged was the AxisEngine.send() method (not receive()
). Shouldn't both chains be available by the time this get called by the
MessageReceiver ?
If so merging in the begining should not be a problem.
Woops, my bad - I misinterpreted the patch. Yes, you're
Hi Glen,
Since TransportSender already extend the Handler interface it can be
easily attached to the end of the handler chain. But MessageReceiver is
a seperate interface and this does not extend Handler.
Are you suggesting that the MessageReceiver should extend the Handler
interface. (also this
Hi All,
There seems to be a bug in the AxisEngine.resume() method (which was recently added)
Wihtin this, only the currently attached execution chain is resumed.
But AxisEngine.send() method attachs two execution chains
(service specific and global) and invoke both. Because of this if
pausing
