Employee (contains employee name, age, phone#, etc.) Server (contains getEmployee() function that returns Employee object) Client (Client.getEmployee() calls Server.getEmployee() via SOAP request)
Do you use wdsl2java to generate these java classes, or do you handcode them? Are you using beanSerializer for automatic serialization/deserialization of things like class Employee?
Bill
Michael Schuerig wrote:
One thing that didn't become clear for me during this thread is why people are using java2wsdl at all. When I started with Axis and web services, I, too, had the idea of making Axis generate the "right" WSDL for me automagically. I've given up on this idea since. I don't object to generating wsdl from a programming language in general, but to my mind, in cases where interoperability is of supreme importance, a WSDL definition is the starting point. [1]
The mapping between Java and WSDL involves some loss in either direction; the two languages are different in expressiveness and in what they emphasize. In particular, I wouldn't expect roundtrip mapping to give sensible results.
Michael
[1] http://webservices.xml.com/pub/a/ws/2003/07/22/wsdlfirst.html
