I seriously advise the WSDL-first approach - if you have that option. The only time I'd use Java2WSDL is if I have an *existing* Java API that I want to "expose" as a web service. When I first started playing around with Axis, I broke my head over the Java-first approach for weeks... then I switched to WSDL-first and it worked like a dream. The WSDL is the "contract" for your web service - the fact that it's Java + Axis that implements it behind the scenes is purely incidental.
Just FYI I have several webservices with Axis 1.2 and VB .NET as both clients and servers, and interop has worked like a dream so far. The editor I use for WSDL is Cape Clear's free SOA editor - http://www.capescience.com/soa/index.shtml. PS one more advantage of WSDL-first is that you learn *much* more... > -----Original Message----- > From: Dr Janusz Martyniak [mailto:[EMAIL PROTECTED] > Sent: Friday, October 07, 2005 18:20 > To: axis-user@ws.apache.org > Subject: RE: soapenc:string rather then xsd:string ? > > > On Fri, 7 Oct 2005, Grossberger, Guenter wrote: > > > Hi! > > > > Although Sunil is right about starting from a WSDL you can > still use Java2WSDL but you have to select "document" style > and "literal" use or even better "wrapped" style instead of > rpc/encoding. > > > > Best regards, > > > > Thanks Guenter, > > I discovered these ( -y and -u) options and I'm fighting > with an axis > client at the moment. > cheers JM > -- > ************************************************************** > ********* > * Janusz Martyniak TEL +44 (0)207 594 > 7810 * > * HEP Group, Physics Dept. FAX: +44 (0)207 823 > 8830 * > * Blackett Lab, Imperial College, Prince Consort Rd, LONDON > SW7 2BW * > ************************************************************** > ********* >
