On Wed, 27 Jun 2007 21:10:39 +0200 "Francois Hornoy" <[EMAIL PROTECTED]> wrote:
[...] > I mean, in the book, there are only simple examples. Remote methods only > take basic datatypes as arguments (int, string, float, no argument.. or > sequence of those) and return values (int, string, float, void..). These inputs and outputs can be as complex as you need them to be, if expressable using XML schema. > > In my code, i want to get an instance of a class as argument, and return an > instance of another class. So i wonder how to specify this in WSDL. Well, you cannot pass around 'instances', that kind of things is handled better by a clustering solution, examine Terracotta for example. In web services you need to come up with a way of serializing this object's salient information into XML. The XML travels over the wire and an object is reconstituted at the other end by populating a new object with this information -- generally referred to as marshalling/demarshalling: http://www.serviceoriented.org/object_marshalling.html If manual schema creation per object type does not appeal to you (the WSDL2Java approach) there is a Java2WSDL tool that will autogenerate this mapping from your class definition -- but this is generally considered to be more error prone when dealing with endpoints that aren't also Java+Axis (it depends on your objects though). Tim ----------------------------------------- Tim Freeman - [EMAIL PROTECTED] http://www-unix.mcs.anl.gov/~tfreeman/ Grid Search: http://www.gridindex.org
