Although i think that generated stubs are going to be the mainstay of J2EE Web service client development.But using generated stubs(or any other JAX-RPC API)occasionally create problems when making them work with other Web service platforms.IMo Web services interoperablity has not been fully addressed by Web service technologies (YET).SOAP and WSDL certainly go a long way toward interoperability,but there are enough 'coner cases' to cause at least a few interoperability headaches. Any comments. [ December 05, 2003: Message edited by: Amer Khan ]
<i>Dare to dream - everything that exists today,was once a figment of someone's imagination, nobody says tomorrow can't be a figment of your today.</i>
I agree...early on when I was contemplating a book a colleague and mine tried to interact with a Web Service I built with Axis and his Python implementation. We had a rough go of it... Be careful of where the problems are though...in some cases the problems are merely in WSDL and having a common way to describe a complex type. A lot of this stuff is being ironed out. Keep an eye on WS-I (Interoperability) http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm This should help quite a bit. I haven't enjoyed the stub regens for versions and all of the WSDL incompatibilities when you try to do more complex operations. Between WS interop limitations and JDO problems, I have flattened many an interface...
Paul B. Monday<br />Author, Web Service Patterns: Java Edition