error while consuming wsdl file with external xsd reference
Hi,
We are facing issue while consuming WSDL file with xsd reference. It shows error as “could not load WSDL document content:web” while using document URL option in connector wizard.
We have uploaded XSD and WSDL files to service export directory and tried to provide WSDL path in the wizard.
Please suggest pointers to resolve the issue.
Pegasystems Inc.
AU
If you change the XSD references to be relative to the WSDL, I've found this doesn't occur.
Usual procedure I use to import is to:
- Copy the WSDL into a file and save in a hosted location
- Copy any linked XSD references to the same location
- Update the WSDL (and XSD's if there are nested includes) to be relative paths
- Import
Infosys
US
PEG
IN
Could you please let me know which version of PRPC you are in? And also please copy the screenshot of the error along with stacktrace?
Infosys
US
We are using PRPC 6.2.
Error: Could not load WSDL document content: web
We have tried giving dynamic reference for all XSD files referred in WSDL as file://web:/StaticContent/global/ServiceExport/<FileName>.xsd and uploaded all XSD files to service export directory
If we copy paste content of the XSD file into WSDL and remove reference from WSDL, we are able to consume WSDL. But this is very time consuming and error prone task.
What is the error you are seeing in the PegaRULES logs. Can you share the snippet of the exception from the PegaRULES logs?
Try changing the import statement in the XSD to use the "service export" directory of Pega and then upload the files to the server:
<xs:include schemaLocation="///MyServiceExportDirectory/MyFile.xsd"/>
MyServiceExportDirectory is the upload folder, MyFile is the XSD filename
Here are few hits on similar issue before:
Pegasystems Inc.
US
The behavior described may be a result of protection against XXE vulnerabilities (see XML External Entity (XXE) Processing - OWASP for a quick synopsis of XXE vulnerabilities) since relative paths are working for you.
StellarNexus Consulting UG
DE
The easiest approach would be to upload the xsds in place of wsdl first.Pega uploads it to the Server but will say that it cannot parse the xsd(which is obvious since we are using a wizard where it looks for wsdls(with/without xsd imports).Once all the xsds which are referenced in your wsdl are uploaded,Try uploading the wsdl now and it should work fine.(This is a work around, which is easy too )