Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to consume WSDL that have external XSD references

SA-18325

Summary



When attempting to import data mapping rules via XSD which contains another XSD reference, none of the import wizards are able to consume the file. The error messaage generated is: "WSDL Parser was unable to find any valid Service definitions in the document"


Error Messages



WSDL Parser was unable to find any valid Service definitions in the document.


Steps to Reproduce

  1. Launch Create Soap Integration Wizard in connectors by navigating through Designer Studio>Integretion>Connectors>Create SOAP Integration wizard.
  2. Use upload the WSDL via URL option.
  3. Input the URL to import the WSDL file.
  4. Supply the authentication params and hit Next to get the error message.


Root Cause



The root cause of the issue is identified as a defect in custom application code or rules. 

The endpoint URL is missing from the WSDL file being imported. WSDL file without endpoint URL cannot be consumed by SOAP Integration wizard or Connector and Metadata accelerator although it might work with SOAP-UI.
 

Resolution



Both SOAP Integration wizard and Connector and Metadata accelerator in PRPC requires a WSDL file to have reference to an endpoint URL for a successful import.
Following is a sample snippet for specifying endpoint URL in WSDL file:

<wsdl:service name="ServiceName">
   <wsdl:port name="ServiceNameBinding" binding="tns:ServiceNameBinding">
      <soap:address location="http://localhost:8080/webservice/ServiceName"/>
   </wsdl:port>
</wsdl:service>
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us