A service impl can invoke other services, while preparing the response, but sharing a single session store across multiple services may be difficult, unless they all are running within the same engine.
With my limited understanding of BPEL and MEP, I see the following scenario here. Root context: Engine (has the following two branches) Processor related contexts (not in exact order): Service, Operation, Module, Handler Process related contexts (not in exact order): (BPEL?), Session / Conversation, MEP, Message I also think that BPEL context is outside the SOAP engine, but the session / conversation or even the message might have references to BPEL Process context, if I can guess. The Axis engine can choose to ignore BPEL context info, however. - venkat On 4/18/05, Aleksander Slominski <[EMAIL PROTECTED]> wrote: > Sanjiva Weerawarana wrote: > > >ARGH .. YAGNI??? > > > >Of course something like a BPEL impl does not need to keep state > >at that level, but for a single service, IMO it'll be far less > >confusing if we say that session = "usage of a service". That's > >consistent with the common usage of the term "session" and in > >any case easier for people to understand. > > > >If you would like to build a higher level thing we could consider > >it but I definitely don't want to mix that with session. The > >higher level thing is exactly like a BPEL process context right? > >In that case my intuition is that it belongs outside the SOAP > >engine, but I could be convinced otherwise. > > > > > i think you are right that it is now out of AXIS2 scope (it will make > things complicated) but it would be good to have some hooks in engine to > facilitate BPEL processor integration - it needs to be integrated very > tightly or you finish with mess of leaky layers of abstractions IMHO ... > > alek > > >----- Original Message ----- > >From: "Glen Daniels" <[EMAIL PROTECTED]> > >To: <[email protected]> > >Sent: Friday, April 15, 2005 5:52 PM > >Subject: Re: Fw: [Axis2] Purpose Deployment changes > > > > > > > > > >>Hi Sanjiva! > >> > >>No, session is "more global" than service - can't a session include > >>calls to multiple services (it can in Axis 1...)? > >> > >>--G > >> > >>Sanjiva Weerawarana wrote: > >> > >> > >>>Hi - not sure whether this went out; mail trouble. Sorry if its dup. > >>> > >>>Sanjiva. > >>> > >>>----- Original Message ----- > >>>From: "Sanjiva Weerawarana" <[EMAIL PROTECTED]> > >>>To: <[email protected]> > >>>Sent: Friday, April 08, 2005 12:23 PM > >>>Subject: Re: [Axis2] Purpose Deployment changes > >>> > >>> > >>> > >>> > >>> > >>>>Wrong order? Engine -> Service -> Session -> MEP -> Message ?? > >>>> > >>>>Sanjiva. > >>>> > >>>>----- Original Message ----- > >>>>From: "Glen Daniels" <[EMAIL PROTECTED]> > >>>>To: <[email protected]> > >>>>Sent: Thursday, April 07, 2005 7:46 PM > >>>>Subject: Re: [Axis2] Purpose Deployment changes > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>Dammit, missed one. :) > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>EngineContext -> > >>>>>>SessionContext -> > >>>>>> > >>>>>> > >>>>>ServiceContext -> > >>>>> > >>>>> > >>>>> > >>>>>>MEPContext (OperationContext) -> > >>>>>>MessageContext > >>>>>> > >>>>>> > >>>>>--Glen > >>>>> > >>>>> > >>>>> > >>> > >>> > > -- > The best way to predict the future is to invent it - Alan Kay > >
