Ask a Question

Unable to load https wsdl

SOLVED
SteveGregory
Occasional Contributor

Re: Unable to load https wsdl

I made a discovery @KarelHusa (and @richie)!

The original, raw wsdl file contains the following include:
<xsd:include schemaLocation="MyServiceSchema.xsd"/>
..but when getting the .wsdl from the server using the ?wsdl suffice, I get this automatically rewritten version:
<xsd:include schemaLocation="http://my.org:80/MyWebService?xsd=xsd0"/>
So it's clearly not a SoapUI issue. The relative URL is being made absolute (with the undesirable protocol) by the IBM AppConnect engine and SoapUI is just following orders.
I'm confident the answer isn't in the WSDL, but I've attached it (The forum said the .wsdl file type was not supported to upload, so I renamed it as an .xml.) in case you think there might be a chance something in it could control the engine's behavior in this way. I didn't bother uploading the schema file (MyServiceSchema.xsd) as it does not reference any other files (i.e. does not contain "include" or "import").

At this point, it seems I should leave the SmartBear forum and go visit an IBM forum.

cancel
Showing results for 
Search instead for 
Did you mean: