RE: soapenc:string rather then xsd:string ?
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, -- DI Günter Grossberger Consultant Tel: +43 1 329 50 161 Software AG Österreich Fax: +43 1 329 50 171 Guglgasse 7-9 GSM: +43 676 833 29 261 1030 Wien http://www.softwareag.com/austria -Original Message- From: Sunil D'Monte [mailto:[EMAIL PROTECTED] Sent: Friday, October 07, 2005 12:33 PM To: 'axis-user@ws.apache.org' Subject: RE: soapenc:string rather then xsd:string ? Is it possible for you to skip Java2WSDL altogether? The recommended approach for interoperability is to hand-code the WSDL (there are editors to help you do this). You could then run the WS-I testing tool to check whether your WSDL really is interoperable. If you do this, then nobody should have any problems using your WSDL... Regards, Sunil PS I believe WS-I forbids soapenc: type of encoding... everything must be defined using XML schema datatypes only. -Original Message- From: Dr Janusz Martyniak [mailto:[EMAIL PROTECTED] Sent: Friday, October 07, 2005 15:46 To: axis-user@ws.apache.org Subject: soapenc:string rather then xsd:string ? Hi all, In my Java2WSDL generated wsdl (axis 1.2) axis uses soapenc:string as a type. Older version of axis seemed to use xsd:string. Can I revert this behaviour in the generation step? My colleague has problems using my wsdl in his workflow engine. any help will be greatly appreciated 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 * ** *
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 * ***
RE: soapenc:string rather then xsd:string ?
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 * ** *
