Solved
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 ...
Forum Discussion
Hey SteveGregory,
Just asking some stupid questions to make sure i understand ok:
1. Youre attempting to create a new SOAP project via the .wsdl and its
2. The .wsdl does include schema references (its not mandatory)
3. The schema references are of the "import" type....i.e. the schemas arent embedded within the .wsdl itself
4. This is for a test environment, right? So editing the .wsdl is possible (if what you were doing was in "live" rather than a test environment, my suggestions wouldnt work)
If i understand correctly i think off the top of my head you have a couple of options relating to editing the .wsdl
1. Change the supported protocol from http to https so that the import uses https (im assuming you can do this although i dont know how to do this myself as ive never done it before)
OR
2. Download the .xsds you need and edit the .wsdl so that the schemas are embedded in .wsdl rather than leave them as using the import option (ive done this before....its not too diffcult, but its easy to make a mistake)
OR
3. Download the .xsds you need and edit the .wsdl so that the .xsd locations are in locations you define that are available via http (when i did this before i just stuck the .wsdls in a shared directory in dropbox).
Out of the 3 options ive mentioned above option 1 would be quickest/easiest, but ive no idea how to do it.
Option 2 is the most difficult, so i think id go for option 3 (which is pretty simple too), unless you know how to do option1
The above is the way id handle it....the other forum people might have some better options to try
Nice one!
Rich
Just asking some stupid questions to make sure i understand ok:
1. Youre attempting to create a new SOAP project via the .wsdl and its
2. The .wsdl does include schema references (its not mandatory)
3. The schema references are of the "import" type....i.e. the schemas arent embedded within the .wsdl itself
4. This is for a test environment, right? So editing the .wsdl is possible (if what you were doing was in "live" rather than a test environment, my suggestions wouldnt work)
If i understand correctly i think off the top of my head you have a couple of options relating to editing the .wsdl
1. Change the supported protocol from http to https so that the import uses https (im assuming you can do this although i dont know how to do this myself as ive never done it before)
OR
2. Download the .xsds you need and edit the .wsdl so that the schemas are embedded in .wsdl rather than leave them as using the import option (ive done this before....its not too diffcult, but its easy to make a mistake)
OR
3. Download the .xsds you need and edit the .wsdl so that the .xsd locations are in locations you define that are available via http (when i did this before i just stuck the .wsdls in a shared directory in dropbox).
Out of the 3 options ive mentioned above option 1 would be quickest/easiest, but ive no idea how to do it.
Option 2 is the most difficult, so i think id go for option 3 (which is pretty simple too), unless you know how to do option1
The above is the way id handle it....the other forum people might have some better options to try
Nice one!
Rich
1 I'm unsure what you meant by "and its", but I'm in SoapUI 5.5.0 and I click on the SOAP icon or do File / New Soap Project, and then enter the URL of the WSDL in the "Initial WSDL" field, and hit "OK".
2 Yes, the WSDL contains:
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://my.name.space/" version="1.0">
<xsd:include schemaLocation="mySchema.xsd"/>
</xsd:schema>
</types>
As you can see, it is a relative location (in the same folder as the wsdl) so I'm confused why it uses the server and path from the WSDL's URL but changes the protocol.
3 Not embedded, but "include" rather than "import".
4.1 I'm not sure what you mean about changing the "supported protocol". There is an entry that reads:
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
..but when I changed that to ../soap/https"/> it broke something in the flow and wouldn't build.
(My web service is running in IBM AppConnect.)
4.2 IBM AppConnect requires the schema be separate from the WSDL, so no can do.
4.3 I don't believe I have an unsecured server available, and having a schema file separate from the web service server, that would need to be kept synchronized with the schema file in the app if there are changes, would be added maintenance and risk.
Of those, the most promising path of exploration seems to be changing the binding transport to ..https and trying to get rid of the errors it causes elsewhere in the app, but do any of these further details give you any ideas?
Thanks.