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/01/27 06:44:39 UTC
[Apache Web Services Wiki] Updated: FrontPage/OMDiagrams

   Date: 2005-01-26T21:44:38
   Editor: EranChinthaka
   Wiki: Apache Web Services Wiki
   Page: FrontPage/OMDiagrams
   URL: http://wiki.apache.org/ws/FrontPage/OMDiagrams

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -7,29 +7,29 @@
  * Light weight.
  * Stores only the portions read. Rest is in the original stream.
 
- [http://nagoya.apache.org/~dims/axis2/OMDiagrams/conversion.GIF http://nagoya.apache.org/~dims/axis2/OMDiagrams/conversion.GIF]
+ [http://www.apache.org/~chinthaka/axis2wiki/conversion.GIF http://www.apache.org/~chinthaka/axis2wiki/conversion.GIF]
 
 == Serializer ==
 Accepts an object and generates push (e.g. SAX) events that will be transformed into either 
  * The OM by the OM writer or
  * To a stream by the stream writer.
 
- [http://nagoya.apache.org/~dims/axis2/OMDiagrams/serialization.GIF http://nagoya.apache.org/~dims/axis2/OMDiagrams/serialization.GIF]  
+ [http://www.apache.org/~chinthaka/axis2wiki/serialization.GIF http://www.apache.org/~chinthaka/axis2wiki/serialization.GIF]  
 
 == Deserializer ==
 A genetrated code that deserializes the stream to an object(s) by using the pull model.
 
- [http://nagoya.apache.org/~dims/axis2/OMDiagrams/deserialization.GIF http://nagoya.apache.org/~dims/axis2/OMDiagrams/deserialization.GIF]  
+ [http://www.apache.org/~chinthaka/axis2wiki/deserialization.GIF http://www.apache.org/~chinthaka/axis2wiki/deserialization.GIF]  
 
 == Message inflow (At server or client) ==
 The following diagram explains the typical conversions that happen during processing inside the axis engine. This can take place either is the server, receiving the request or the client, receiving the response.
 
- [http://nagoya.apache.org/~dims/axis2/OMDiagrams/inflow.GIF http://nagoya.apache.org/~dims/axis2/OMDiagrams/inflow.GIF]  
+ [http://www.apache.org/~chinthaka/axis2wiki/inflow.GIF http://www.apache.org/~chinthaka/axis2wiki/inflow.GIF]  
 
 == Message outflow (At server or client) ==
 The following diagram explains the typical conversions that happen during the processing inside the axis engine. This can take place either at the server, sending the response or at the client, sending the request.
 
- [http://nagoya.apache.org/~dims/axis2/OMDiagrams/outflow.GIF http://nagoya.apache.org/~dims/axis2/OMDiagrams/outflow.GIF] 
+ [http://www.apache.org/~chinthaka/axis2wiki/outflow.GIF http://www.apache.org/~chinthaka/axis2wiki/outflow.GIF] 
 
 == Proposed OM Architecture ==
 The following will explain what is in AXIOM and what is out of the AXIOM.