Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSDL import does not import XSDs #12772

Open
1 task done
Harm10 opened this issue Apr 5, 2024 · 1 comment
Open
1 task done

WSDL import does not import XSDs #12772

Harm10 opened this issue Apr 5, 2024 · 1 comment

Comments

@Harm10
Copy link

Harm10 commented Apr 5, 2024

Is there an existing issue for this?

  • I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

When I import our wsdl structure from a local folder I get this error message in my generated Response:
The element or type could not be found FinancieelBeeldKlant_Rpy

The wsdl contains this structure:

wsdl:types
<xsd:schema targetNamespace="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.schemas.rabobank.nl/Wonen/akl/FinancieelBeeldKlant/01/Req" schemaLocation="FinancieelBeeldKlant_Req.xsd"/>
<xsd:import namespace="http://www.schemas.rabobank.nl/Wonen/akl/FinancieelBeeldKlant/01/Rpy" schemaLocation="FinancieelBeeldKlant_Rpy.xsd"/>
</xsd:schema>

If I use the exact same wsdl in SOAPUI I do not get this message. It looks like SOAPUI replaces the location in the wsdl if the imported wsdl is from another location so it also finds the xsds.
My local folder also contains the 2 mentioned xsds.

This seems to be a problem since wsdl import support was added to Postman.
Should it work? If so, what am I doing wrong? If not, can the same logic as SOAPUI be applied?

Steps To Reproduce

Import a WSDL from a local folder also containing the XSDs

Screenshots or Videos

No response

Operating System

Windows

Postman Version

10.24

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

@VShingala
Copy link
Member

@Harm10 Thanks for reporting the issue! It seems there is an issue with importing WSDL file having references to other files. In such cases other referenced files are not resolved correctly ATM. We're looking into this and update here once we have a fix for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants