Fetch WSDL Error

Not applicable

Hi,

I'm attempting to create a new API proxy and I'm having difficulty importing the WSDL for the service.

The WSDL source is:

https://xml.accurateappend.com/Products/phoneappend.asmx

The error message is:

Fetch WSDL Error: Expected root element '{http://schemas.xmlsoap.org/wsdl/}definitions' for the WSDL document but was '${token.name}'.

As a debugging measure I have attempted to save the WSDL to a file and import too.

Can someone point me in the right direction?

Thanks,

Chris

Solved Solved
0 3 965
1 ACCEPTED SOLUTION

Not applicable

Hi @Chris Nichols,

The UI is having a problem because of lines like this in the WSDL:

<wsdl:message name="PhoneAppend_ResidentialHttpGetOut">

<wsdl:part name="Body">

</wsdl:message>

The problem is there is no type for the wsdl:part. If I change the code to instead be like this (there are 4 similar cases in the WSDL you cited), it works:

  <wsdl:message name="PhoneAppend_ResidentialHttpGetOut">
    <wsdl:part name="Body" type="s:string"/>
  </wsdl:message>

We need the type for input parameters, but I don't think we need them for output parameters, so we should be able to remove this requirement.

In the meantime can you hand-modify your WSDL and try importing that?

Thanks,

Charles

View solution in original post

3 REPLIES 3

Not applicable

@Chris Nichols, I can confirm that the WSDL at https://xml.accurateappend.com/Products/phoneappend.asmx?WSDL causes an error, whether attempting to load it via URL or file. But where are you seeing that error message? All I see is "Fetch WSDL Error: Error processing WSDL."

This is the only error I'm receiving from the Apigee GUI but it does prevent me proceeding to the step and therefore prevents the proxy build.

Not applicable

Hi @Chris Nichols,

The UI is having a problem because of lines like this in the WSDL:

<wsdl:message name="PhoneAppend_ResidentialHttpGetOut">

<wsdl:part name="Body">

</wsdl:message>

The problem is there is no type for the wsdl:part. If I change the code to instead be like this (there are 4 similar cases in the WSDL you cited), it works:

  <wsdl:message name="PhoneAppend_ResidentialHttpGetOut">
    <wsdl:part name="Body" type="s:string"/>
  </wsdl:message>

We need the type for input parameters, but I don't think we need them for output parameters, so we should be able to remove this requirement.

In the meantime can you hand-modify your WSDL and try importing that?

Thanks,

Charles