It's invalid. The first schema must <import> the second to make it valid.
Jeff Dies Koper wrote: > Have you tried running it through a validating parser? > Please try and post the result. > #I could try if you post the whole WSDL before I go home tonight. > > Regards, > Dies > > Jarmo Doc wrote: > >> My WSDL document, generated directly from Java via Axis 1.3 java2wsdl, >> is structured something like this: >> >> 01. <wsdl:definitions targetNamespace="a.b.c" xmlns:tns2="x.y.z"> >> 02. <wsdl:types> >> 03. <schema elementFormDefault="qualified" targetNamespace="a.b.c"> >> 04. <element name="fault" type="tns2:MyFault"/> >> 05. </schema> >> 06. <schema elementFormDefault="qualified" targetNamespace="x.y.z"> >> 07. <complexType name="MyFault"> >> 08. ... definition here ... >> 09. </complexType> >> 10. </schema> >> 11. </wsdl:types> >> >> This WSDL appears to be quite acceptable to Axis' wsdl2java and to the >> gSOAP equivalent. However, WebSphere's wsdl2java does not like it. >> Specifically it complains that tns2:MyFault on line 04 cannot be resolved. >> >> So, a few questions: >> >> 1. is the type definition for MyFault on line 07 correct? I had assumed >> that it was implicitly in namespace x.y.z because that is the >> targetNamespace of the enclosing schema (line 06) and hence does not >> need to be explicitly decorated with tns2. >> >> 2. Generally, is it valid to reference MyFault in schema #2 from schema >> #1 in this way? >> >> 3. Any idea if this is a bug in WebSphere wsdl2java or in Axis java2wsdl? >> >> Thanks. >> > > > >
