geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@opensource.lk>
Subject Re: [Axis2][Revisit]How about making Message context executable?
Date Wed, 09 Mar 2005 15:03:41 GMT
Um, Srinath wrong list? ;-)

Sanjiva.

----- Original Message ----- 
From: "Srinath Perera" <hemapani@gmail.com>
To: <dev@geronimo.apache.org>
Sent: Monday, March 07, 2005 3:49 PM
Subject: [Axis2][Revisit]How about making Message context executable?


> Hi All;
>
> I put this Q about making the MessageContext executable?  I do not get
> a clear response ..
> May be it does not call for enough attention?
>
> But I feel this is bit too bigger change to do without enough
> community input .. So I feel we should hold it back for the F2F. But
> then "pause the engine execution at some state" should wait too
> thoughts?
> Srinath
>
> ---------- Forwarded message ----------
> From: Ajith Ranabahu <ajith.ranabahu@gmail.com>
> Date: Fri, 4 Mar 2005 16:49:43 +0600
> Subject: Re: [Axis2]How about making Message context executable?
> To: axis-dev@ws.apache.org, Srinath Perera <hemapani@gmail.com>
>
>
> Hi there Srinath and all,
> This is probably a complete 180 degree turn from where we were heading
> (well not exactly a backward leap, but a drastic change in direction).
> The Message Context (MC) was pursued only as a property bag. Now we
> are trying to put executable actions there! So the role of the MC is
> changed now. I am not sure what this means to the structure of axis.
> I guess this needs to be thought out carefully.
> BTW if we are to do such a change this is the best time to tackle such
> a change. It will be impossible on later stage.
>
>
> On Thu, 3 Mar 2005 17:54:59 +0600, Srinath Perera <hemapani@gmail.com>
wrote:
> > Hi All;
> >
> > This is regarding the invoke, pausing and resuming the the invocation!
> >
> > To this point this is implemented with an ExecutionChain kept in the
> > MessageContext ..calling the invoke on the MessageContext.
> >
> > But more I look at the code more I convinced the way the Glen has done
> > it in EngineToy by putting the invoke(), resume() and pause() in the
> > MessageContext would yield simpler and better code. Only catch is that
> > it will make the MessageContext executable .. making it bit away from
> > what we percive about it!
> >
> > thoughts?
> >
> > I have a bit more revolutionary proposal to add (hope I will not
> > killed for saying this :D ) that is to get rid of the AxisEngine and
> > put the send and receive in to the MessageContext. Making it our
> > approach is to create the information bag, messageContext and ask it
> > to send(), recive(), pause() .. I just want to know what people think
> > about this?
> >
> > Thanks
> > Srinath
> >
>
> --
> Ajith Ranabahu
>


Mime
View raw message