svn commit: r154794 - webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html

[de...@apache.org]

Author: deepal
Date: Mon Feb 21 21:20:08 2005
New Revision: 154794

URL: http://svn.apache.org/viewcvs?view=rev&rev=154794
Log: (empty)


Modified:
    webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html

Modified: webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html?view=diff&r1=154793&r2=154794
==============================================================================
--- webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html (original)
+++ webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html Mon Feb 21 21:20:08 2005
@@ -26,7 +26,7 @@
 <p>Just like Axis 1.x family Axis2 is all about Message processing. It is important to note that Axis2 is not just about encoding of the messages from Java to XML and vise versa. Axis is a framework for the Web Service stack. All other components WS-Security, WS-RM ect of the Web Service stack fits in to Axis via the extension mechanism of the the Apache Axis. Apache Axis is a framework for Web Service Stack.Axis SOAP Message processing with always start by running the information holder called MessageContext through the extension mechanism of the Axis. This make the Axis and generic framework for All the Web Service add on services.</p>
 
 <h3>Extension Mechanism</h3>
-<p>The extension mechanism of the Axis is built with two types of components called Handlers and the Phases. The Phases are place Holders for the Handlers and they can be configured via the configuration mechanism of the Axis. When a Web Service is invoked Engine will order the registered Handlers inside the Phase, on which each handler belongs. Once the handlers are assign to the phases the phases are invoked in the order and in turn each Phase will invoke the contained Handlers.</p> 
+<p>The extension mechanism of the Axis is built with two types of components called Handlers and the Phases. The Phases are place Holders for the Handlers and they can be configured via the configuration mechanism of the Axis. When a web service is deployed Phase-Resolver will order the registered Handlers in side a phase and phases will be ordered according to the configurations. When a web service is invoked Engine will preserved the order of handlers. Once the handlers are assign to the phases the phases are invoked in the order and in turn each Phase will invoke the contained Handlers.</p> 
 
 <p>The Axis contains some built in Handlers that drives the service invocation, yet the user can add new Handlers via the deployment Mechanism. The new Handlers will fit in to the Phases in the Execution Chain according to the Phase rules that specified with each the Handler.</p>