Unable to load https wsdl
SOLVED- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to load https wsdl
When I try to create a new SOAP project and feed it a WSDL with an https URL (e.g. https://server/path/webservice?wsdl), the WSDL loads fine, but SoapUI tries to load related XSD files with the http protocol. The server hosting the web service does not allow http, thus I always get the following error and cannot create a SOAP Project:
Error loading WSDL
There was something wrong with the WSDL you are trying to import
Error loading [http://server/path/webservice?xsd=xsd0]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected end of file after null
I am using SoapUI 5.5.0. Please advise.
Solved! Go to Solution.
- Labels:
-
SOAP
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.

- « Previous
-
- 1
- 2
- Next »
- « Previous
-
- 1
- 2
- Next »