Changes between Version 3 and Version 4 of ExampleUsingXmlRpcCompliantTypes

Timestamp:

05/22/07 12:17:48 (17 years ago)

Author:

lauer

Comment:

--

ExampleUsingXmlRpcCompliantTypes

@@ -1 +1 @@
 == Using XML-RPC compliant types in your API ==
 
-If you use types in your remote calls wich are XML-RPC compliant things are very easy:
+If you use types in your remote calls which are XML-RPC compliant things are very easy:
 
 '''Server side'''
 
- - The server side defines an API to be used remotely over XML-RPC. Additionaly an implementation
+ - The server side defines an API to be used remotely over XML-RPC. Additionally an implementation
    of the API is hosted on the server-side
    
@@ -11 +11 @@
 interface Api {
   String getStatusMessage( int code );
+  int[] getInts();
 }
 
 class Impl implements Api {
   public String getStatusMessage( int code ) {...}
+  public int[] getInts() { return new int[]{ 1,2,3 }; }
 }
 }}}
@@ -33 +35 @@
 Api remote_api = XmlRpc.createClient( Api.class, "handlerId", host, port );
 String msg = remote_api.getStatusMessage( 42 );
+int[] ints = remote_api.getInts();
 ...
 }}} 
@@ -43 +46 @@
 
  - instead of solely using java type Hashtable for XML-RPC type STRUCT, also java type Map can be used. 
+
+ - arrays of convertible types including their primitive counterparts (such as Integer, int, ...) can be used out-of-the-box