Re: WSDL2Java

- Original Message - > > Looks like it's time to break down and buy a copy of XML Spy! Its wsdl > editor and schema valudation would've probably caught these things... > XML Spy can catch broken QNames, which was the primary problem with the original WSDL. Omniopera can too (use its "Fin

Re: XML instead of WSDL?

t; instead of the WSDL document or a combination of both when creating a > web service using Axis? WSDL already uses XML Schema to specify the types of the message parts involved in a web service. The "types" element of the WSDL document contains a schema which can contain any types y

Re: another WSDL2Java-problem: no stubs / skeletons emitted

pace. Your namespace prefix "soap" should be defined as: xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/ whereas you have: xmlns:soap=http://schemas.xmlsoap.org/soap/encoding/ Hope that helps. Regards, -- James Yegerlehner Omniopera: XML Schema and WSDL Authoring Software http://www.o

Re: WSDL Question

ma namespace: http://www.w3.org/1999/XMLSchema You should use that of the W3C recommendation: http://www.w3.org/2001/XMLSchema Regards, -- James Yegerlehner Omniopera: XML Schema and WSDL Authoring Software http://www.omniopera.com

Re: WSDL2Java problems with .NET WSDL

tml and here's a step-by-step on how you automatically create a .NET web service skeleton from WSDL: http://www.omniopera.com/HowDoISimpleServiceMSDotNet.html Regards, James Yegerlehner Omniopera: XML Schema and WSDL Authoring Software http://www.omniopera.com - Original Message