axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r568596 - /webservices/axis2/branches/java/1_3/modules/documentation/xdocs/@axis2_version_dir@/Axis2-rpc-support.xml
Date Wed, 22 Aug 2007 12:47:58 GMT
Author: amilas
Date: Wed Aug 22 05:47:58 2007
New Revision: 568596

update the document


Modified: webservices/axis2/branches/java/1_3/modules/documentation/xdocs/@axis2_version_dir@/Axis2-rpc-support.xml
--- webservices/axis2/branches/java/1_3/modules/documentation/xdocs/@axis2_version_dir@/Axis2-rpc-support.xml
+++ webservices/axis2/branches/java/1_3/modules/documentation/xdocs/@axis2_version_dir@/Axis2-rpc-support.xml
Wed Aug 22 05:47:58 2007
@@ -38,7 +38,7 @@
 is based on a set of well defined rules. This document aims to
 drill down to the details of the strategy and resolve most of the
 unknown bits and pieces. Note that Axis2 currently does not support
-the rpc/encoded style fully. Its main support is for the rpc/lit
+the rpc/encoded style. But it fully support for the rpc/lit
 <p>We will discuss the Axis2 RPC strategy in the following
@@ -89,11 +89,8 @@
 <li>The children of this element are non namespace qualified
 elements with the part names as local names (referred to as
 <strong>part element</strong>)</li>
-<li>In case the part refers to a standard type like the example
-WSDL, the content of the part element would be of that type. If the
-part refers to a complex type defined in the schema, the content of
-the part element becomes of that type. Having an element reference
-in the part when the binding is rpc is invalid.</li>
+<li>In this case part element should always have a type attribute which referes
+to an valid xml type.</li>
 <p>For example, the input wire message for the echo operation
 mentioned in the above WSDL fragment would look like this:</p>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message