|
(Sorry for the rich text -- but it makes it easier
to show the errors/corrections)
Tamas,
WSDL is such fun! Your errors are caused by WSDL
errors in the Axis and GLUE generated WSDL files. Fortunately, your error
messages tell you where to find the problems.
You have namespace and qname problems in the Axis
WSDL. (This is a known error -- I think it's fixed in the latest build).
In both the GLUE and WASL clients to Axis scenarios
your error messages indicates that you're searching for <element>
descriptions in the default namespace (wsdl:), and you should be looking in
the target namespace of the <schema> section. But you'll notice that
you have no target namespace defined, and your element references in your
<part> elements aren't namespace qualified. (Compare the Axis WSDL to the
WASP and GLUE WSDLs to see the difference.)
Here's an except from your Axis WSDL:
<wsdl:definitions targetNamespace="http://localhost:8080/axis/services/TestService"
xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://localhost:8080/axis/services/TestService" xmlns:intf="http://localhost:8080/axis/services/TestService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <wsdl:types> <schema targetNamespace="" xmlns="http://www.w3.org/2001/XMLSchema"> <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/> <element name="testString" type="xsd:string"/> <element name="echoReturn" type="xsd:string"/> </schema> </wsdl:types> <wsdl:message name="echoRequest"> <wsdl:part element="testString" name="testString"/> </wsdl:message> <wsdl:message name="echoResponse"> <wsdl:part element="echoReturn" name="echoReturn"/> </wsdl:message> The fixed WSDL would look like this:
<wsdl:definitions targetNamespace="http://localhost:8080/axis/services/TestService"
xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://localhost:8080/axis/services/TestService" xmlns:intf="http://localhost:8080/axis/services/TestService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <wsdl:types> <schema targetNamespace="http://localhost:8080/axis/services/TestService" xmlns="http://www.w3.org/2001/XMLSchema"> <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/> <element name="testString" type="xsd:string"/> <element name="echoReturn" type="xsd:string"/> </schema> </wsdl:types> <wsdl:message name="echoRequest"> <wsdl:part element="intf:testString" name="testString"/> </wsdl:message> <wsdl:message name="echoResponse"> <wsdl:part element="intf:echoReturn" name="echoReturn"/> </wsdl:message> There is also an error in the GLUE WSDL file. The
parameterOrder attribute should reference a <part> name ('parameters'),
but instead it references an undefined
name ('testString')
<wsdl:message
name='echo0In'>
<wsdl:part name='parameters' element='tns:echo'/> </wsdl:message> <wsdl:message name='echo0Out'> <wsdl:part name='parameters' element='tns:echoResponse'/> </wsdl:message> <wsdl:portType name='TestService'> <wsdl:operation name='echo' parameterOrder='testString'> <wsdl:input name='echo0In' message='tns:echo0In'/> <wsdl:output name='echo0Out' message='tns:echo0Out'/> </wsdl:operation> </wsdl:portType> It should be:
<wsdl:message
name='echo0In'>
<wsdl:part name='parameters' element='tns:echo'/> </wsdl:message> <wsdl:message name='echo0Out'> <wsdl:part name='parameters' element='tns:echoResponse'/> </wsdl:message> <wsdl:portType name='TestService'> <wsdl:operation name='echo' parameterOrder='parameters'> <wsdl:input name='echo0In' message='tns:echo0In'/> <wsdl:output name='echo0Out' message='tns:echo0Out'/> </wsdl:operation> </wsdl:portType> Best regards,
Anne
|
Title: GLUE-AXIS Interoperability
- More on document/literal and interoperability (WASP/GLUE... Tamas Hauer
- Re: More on document/literal and interoperability (... Anne Thomas Manes
