search

postmanlabs / postman-app-support

Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
https://www.postman.com
5.78k stars 837 forks source link

WSDL import does not import XSDs #12772

Open Harm10 opened 3 months ago

Harm10 commented 3 months ago

Is there an existing issue for this?

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:

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 commented 2 months ago

@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.

natereprogle commented 1 week ago

@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.

Hey there, is there any update to this? I'm trying to import the SOAP definition for Cisco UCM and I can't due to it referencing a single .xsd file, failing to build the entire schema. Thank you!