axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r209205 - /webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html
Date Tue, 05 Jul 2005 03:44:55 GMT
Author: chathura
Date: Mon Jul  4 20:44:54 2005
New Revision: 209205

Data Binding added to Architecture guide


Modified: webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html
--- webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html (original)
+++ webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html Mon Jul  4 20:44:54 2005
@@ -292,6 +292,20 @@
 generate the code. No matter what the language, the process is the same except 
 for the template that is being used.h</p>
+<h2>Data Binding</h2>
+<h3>Integration with the code generation engine</h3>
+<p>Axis2 M2 was released with code generation support but without data binding. The
version 0.9 is shipped with data binding support with complete schema support. Such claim
is made possible because of the fact that the data binding tool, xml-beans, has the full schema
support. The original architecture of the code generation framework did not undergo significant
changes because of the way that the code generation framework was originally designed. Data
binding was incorporated as a pluggable extension to the code generation engine. Version 0.9
does not support SOAP encoding. It only supports the RPC literal or document literal massages.</p>
+<p><img border="0" src="images/codegen.gif"></p>
+<h3>Serialization and Dezerialization</h3>
+<p>Xml-beans supports StaX API and AXIOM is based on a StAX API. Data binding in Axis2
is achieved through interfacing the AXIOM with the Xml-beans using the StAX API which is supported
by both parties. At the time of the code generation there will be supporter classes for each
WSDL operation that will have the utility methods that can deserialize the from AXIOM to data
bound object and serialize from data bound object to AXIOM. For example if the WSDL has an
operation called “echoString”, once the code is generated there will be an
class generated that will have methods that will look like the following.</p>
+<p>public  static  toOM(org.soapinterop.xsd.EchoStringParamDocument
param) : This method will handle the serialization.</p>
+<p>public static org.apache.xmlbeans.XmlObject fromOM(
param, java.lang.Class type) : This method will handle the serialization.</p>
+<p>public static org.apache.xmlbeans.XmlObject getTestObject(java.lang.Class type)
: This will be a utility method that can be used to create sample objects of the given data
bound object.</p>
 <h2>Client API</h2>

View raw message