Changes between Version 3 and Version 4 of ExampleUsingXmlRpcBeans

Timestamp:

10/09/06 14:49:35 (18 years ago)

Author:

lauer

Comment:

--

ExampleUsingXmlRpcBeans

@@ -18 +18 @@
     - a conversion mapping for that type is put at the XmlRpcBean (which then acts as an API itself)
     - it is an XmlRpcBean (that is, XmlRpcBeans can be nested)
+    - it is a Collection or Map containing a type which is XML-RPC compliant and is annotated with the @Contains annotation
+
 
 Technically, an !XmlRpcBean is converted into a XML-RPC STRUCT. The field names of the tranfered map are the property names derived from the bean class.
@@ -54 +56 @@
 }}}
 
+== Client side ==
+
+Again, the client has no restrictions using the bean class:
+{{{
+public interface Api
+{
+    @Contains(CoffeeBean.class)
+    Collection<CoffeeBean> getAllBeans();
+}
+
+Api remote_api = XmlRpc.createClient( Api.class, "handlerId", host, port );
+
+Collection<CoffeeBean> beans = remote_api.getAllBeans();
+
+for( CoffeeBeans b: beans )
+{
+    System.out.println( "Bean of type " + b.getType() + " comes from " + b.getOrigin() );
+}
+...
+}}}
+
 See also [http://delight.opendfki.de/wiki/ExampleUsingOwnConceteTypes#UsingowntypesinCollectionsandMaps How to use own types in Collections an Maps].