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 * > > ************************************************************** > > ********* > > >
