axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Daniels <>
Subject Re: Fwd: [Axis2]let us Discuss Engine
Date Tue, 14 Dec 2004 12:58:57 GMT
I would really like to discuss the engine this week, but I have family 
plans tomorrow evening, and so won't be able to attend the chat at 10PM.

Might people be willing to switch the time this week to the same time as 
last week?  If this is inconvenient for anyone, that's fine - just 
figured I'd ask.


Srinath Perera wrote:
> ---------- Forwarded message ----------
> From: Srinath Perera <>
> Date: Tue, 14 Dec 2004 17:13:17 +0600
> Subject: let us Discuss Engine
> To:
> Hi All;
> I think we decided to discuss engine this week on chat! I am trying to
> explain the engine in prototype2 so that it is easy to find what it
> does.
> A) Engine, Registry & Deployment
> 1) Deployment module will parse the deployment information and create
> an EngineRegistry
> (see the org.apache.axis.engine.EngineRegistry and the
> org.apache.axis.description.*)
> 2) there is a phase resolver (org.apache.axis.phaseresolver) code that
> work on the Registry and create an ExecutionChain and register the
> execution chain in the AxisService
> 3) when the request comes in, the engine will find the service, get
> the ExecutionChain and call the ExecutionChain
> B) In flow
> Inflow starts with an Execution Chain and In flow always ends with a
> Receiver, e.g. SyncInOutReceiver, AsyncInOutReceiver, InReceiver see
> org.apache.axis.impl.receivers. Receiver handles the Sync, Async and
> the In/Inout aspects of the invocation. Receivers call the Providers
> where the providers have the Axis1.1. semantics unchanged.
> c) Out Flow
> Out flow starts with a ExecutionChain and out flow always ends with
> the TransportSender .. e.g. HTTP transport Sender ...... the transport
> sender looks at the Addressing information and if that is missing look
> for the incoming transport information from the received message. (see
> org.apache.axis.transport.AbstractTransportSender )
> D) Contexts
> there are three contexts Global, Session and the MessageContext which
> hold the information of each scope. (see org.apache.axis.context)
> E) Client API /Call
> Simple Call is at the org.apache.axis.client.* ; that is just a hack
> and we need to discuss this!
> Thanks
> Srinath

View raw message