I agree with everyone that the java implementations have been ahead of the c. Also, a whole lot depends on that WSDL. Read the online IBM article about 'Which WSDL should I use?' The service side can make decisions like returning an XML response message all the time instead of throwing an exception. Exceptions tend to be a pain in rearend in different languages including C and ZSI (Python). they work just fine in java. I ended up doing document-literal WSDLs all in java (Axis and now JAX-WS), but the design was often driven by what languages were on the client-side. If we had C++ and Python clients to integrate, the WSDL had to be pretty conservative. On the service-side in java I have even DOM parsed an XML file and filled the autogenerated classes created by the WSDL and XSD.
There are also tricks to changing the service-side ... for example, you can try to nail your interface methods (WSDL) down and only add to your XSD. In some cases existing clients can just keep using the service without re-autogenerating ... but this is the beauty of a cleaner code design which capitalizes on the extensibility and standard parsing of XML. I'd like to know if other companies are doing a good job of managing and versioning their WSDL and XSD files (they should be separate).? or, are they just letting the whole governance and configuration management fall apart.? he he ... I'm laughing pretty hard right now. Well, Sam, perhaps we have now bent your ear with too much information. No matter what, don't feel bad ... there is a lot to learn ... and I swear, you can only learn this junk by doing ... LOL cara On Thu, Apr 2, 2009 at 9:52 AM, Sam Carleton <[email protected]> wrote: > On Thu, Apr 2, 2009 at 11:37 AM, cara <[email protected]> wrote: > >> Sam, >> >> IMHO, it isn't worth doing web services unless you use the autogenerated >> code. I learned from experience to stop hand jamming xml. If your WSDL >> changes, you want to re-autogenerate the plumbing code on both your client >> and server side ... and with any luck, any code changes you have are >> isolated in the code you had to write in order to use the objects generated >> on your client side. > > > Very good point, things will change and using the autogenerated code will > make that far less painful. > > Thank you. > > Sam >
