You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by ge...@ws.apache.org on 2005/02/15 07:07:51 UTC

[Apache Web Services Wiki] Updated: FrontPage/Architecture/Engine

   Date: 2005-02-14T22:07:51
   Editor: SrinathPerera
   Wiki: Apache Web Services Wiki
   Page: FrontPage/Architecture/Engine
   URL: http://wiki.apache.org/ws/FrontPage/Architecture/Engine

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -7,18 +7,10 @@
   * Define the invocation flow of the in/out flow of the engine and provide a implementation. This include implementing the following.
     * Phased Handler resolver.
     * Providers and transport sender.
-  * Provides a Management API.
-  * Implement following scenarios in Axis engine. 
-     1. Implements the void echo() without soap headers.
-     1. Implements the void echo(simpleType) without SOAP Headers.
-     1. Implements void echo(simpleType) with  SOAP Headers no access to the body for handlers.
-     1. Implements void echo(ComplexType) with SOAP Headers no access to the body for handlers.
-     1. Implements void echo(ComplexType) completely with access to the body. 
-     1. Support all the WS-Security requirements.
-  * Providing full Sync, Async support.
+    * Provides a Management API. - Not supported in M1
+    * Providing full Sync, Async support. - partially supported in M1
  
 == Wish List ==
-  * Pooling of the Handlers and the common executers. 
   * Giving the engine ability to stop and restart the execution later. 
 
 == Sub components  ==
@@ -31,7 +23,7 @@
  1. Sync and Async Message flows.
 
 == Handler frame work and Message Invocation ==
-Handler framework consists of Handler ,CommonExecutor interfaces. 
+Handler framework consists of Handler ,Phases and the ExecutionChain
 
 === Handler Interface ===