Topic
  • No replies
SarahWilliams
SarahWilliams
1 Post

Pinned topic WSDLException

‏2010-08-03T10:06:32Z |
Hi
I am trying to consume a Web Service in RAD 6.
I have successfully tested the WSDL from my third party in the Web Services Explorer. This works correctly.
Next I launched the Web Service Client Wizard. This failed with the following message:

Error messages were issued.
WSWS3574E:
FATAL ERRORS ENCOUNTERED ----------

  • GENERATION OF ARTIFACTS HAS BEEN SUSPENDED.*

  • See messages to follow for more details.*

WSWS3491E: Error: Reading import file: WSDLException (at /definitions/binding[1]/operation[1]/input): faultCode=INVALID_WSDL: Encountered illegal extension attribute 'message'. Extension attributes must be in a namespace other than WSDL's.

The WSDL is successfully created in my workspace, but none of the artifacts are created.

An example of the WSDL section that RAD 6 is complaining about is:

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ro="urn:LightingLibrary" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/" xmlns:xs="http://www.w3.org/2001/XMLSchema" name="LightingLibrary" targetNamespace="http://tempuri.org/">
. . .
<binding name="BaseServiceBinding" type="tns:BaseService">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="GetStreets">
<soap:operation soapAction="urn:LightingLibrary-BaseService#GetStreets" style="rpc"/>
<input message="tns:GetStreetsRequest">
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:LightingLibrary-BaseService" use="encoded"/>
</input>
<output message="tns:GetStreetsResponse"> <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:LightingLibrary-BaseService" use="encoded"/>
</output>
</operation>

I have spoken to the third party about these problems and they assure me that the WSDL is correct and valid.
I have successfully consumed this Web Service using asp.net with no problems at all, but for some reason RAD 6 just doesn’t like it!

Any ideas you have would be gratefully appreciated.