You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-dev@ws.apache.org by ha...@apache.org on 2001/10/31 22:51:08 UTC

cvs commit: xml-rpc/xdocs types.xml

hannes      01/10/31 13:51:08

  Modified:    xdocs    types.xml
  Log:
  Added link and some cleanup.
  
  Revision  Changes    Path
  1.3       +6 -6      xml-rpc/xdocs/types.xml
  
  Index: types.xml
  ===================================================================
  RCS file: /home/cvs/xml-rpc/xdocs/types.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- types.xml	2001/10/31 21:35:13	1.2
  +++ types.xml	2001/10/31 21:51:08	1.3
  @@ -9,15 +9,15 @@
     <body>
       <section name="Type Mapping between XML-RPC and Java">
         <p>
  -      The following table explains how data types are converted between their XML-RPC
  -representation and Java.
  +      The following table explains how data types are converted between their <a href="http://www.xmlrpc.com/spec">XML-RPC
  +representation</a> and Java.</p>
   
  -Note that the automatic invocation mechanism expects your classes to take the
  +<p>Note that the automatic invocation mechanism expects your classes to take the
   primitive data types as input parameters. If your class defines any other types
   as input parameters (including java.lang.Integer, long, float), that
  -method won't be usable from XML-RPC unless you write your own handler.
  +method won't be usable from XML-RPC unless you write your own handler.</p>
   
  -For return values, both the primitive types and their wrapper classes work fine.
  +<p>For return values, both the primitive types and their wrapper classes work fine.</p>
   
   <table border="1" cellpadding="5">
   <tr>
  @@ -66,7 +66,7 @@
   <td>byte[ ]</td>
   </tr>
   </table>
  -      </p>
  +
       </section>
     </body>
   </document>