Axis Engine

[Doug Davis <du...@us.ibm.com>]

One of the things we talked about at the F2F (which hopefully
we'll have notes to show everyone - hint, hint 8-) is that
the Axis Engine should know about the transport chains, the
global chains and then the service specific chains.  Right
now each group of chains are called by simply placing the
appropriate handler in the right place, ie:

  Engine->Transport Chain->Global Chain->Service Chain
  or in other words, at the pivot point of the transport
  chains is the handler that kicks offthe global chain. At
  the pivot point of the Global Chain is the handler that
  will invoke the Service Specific chain.

What we talked about doing is something more like:

                                  ->Transport Input Chain
                                  ->Global Input Chain      /->Service
Request Chain
T/L -> AxisEngine/Dispatch Handler->SOAP Engine -------------->SOAP
Semantics/Checks
                                  ->Global Output Chain     \->Service
Pivot Handler
                                  ->Transport Output Chain  \->Service
Response Chain

Here the AxisEngine would call the Transport Input chain, then control
would be returned to the engine, the engine would then call the
global input chain, control would return to the engine, the
engine would then call the SOAP Engine (more on this later),
control would then return to the engine, etc...

The main difference here is that the Engine itself regains control after
each
of the different chains.  The deployment engineer is no longer responsible
for placing the right handler/router at the correct place in the chains.

Also, the SOAP Engine knows about SOAP semantics (see the SOAP
Semantics/Checks call that the SOAP Engine makes) and does the
proper checks at the right time.

Unless someone votes against this change I'd like to go ahead and
make this change to the code base.

-Dug