AnsweredAssumed Answered

Imported XSD's

Question asked by acalbazana on Jan 31, 2019
Latest reply on Jan 31, 2019 by Stephen_Hughes

This is a variant of a question I had a while back...


I have a legacy SOAP service that has imported XSDs in its WSDL definition.  I need help adding a SOAP service to my API Gateway. I am trying to import a WSDL that imports a couple of XSD schemas using relative pathing. The WSDL imports fine, but when I try to access via my client tooling (ReadyAPI), the XSDs do not resolve resulting in a 404 for the imported resource.  I see the 404 in my traffic log.


Any idea on what I need to do in order to enable this?  The provider isn't able to configure the WSDL to make the pathing absolute.  Even if they could... My request still reports a 404 when I try to issue a request for the actual XSD.


I've opened a case for this already, but I'm not getting much traction.  So, I'm opening it up to the community for some more eyes.