SteveGregory
Occasional Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
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.1.7KViews1like0CommentsRe: Unable to load https wsdl
In my (perhaps meager) understanding, the protocol is just a matter of endpoint and what the server allows. Our dev boxes use http and don't support https while our Production environment requires https and doesn't support http. The WSDL and XSD files are not modified between environments. This likely works because all our paths in our WSDL and XSD files are relative. Thanks for trying, richie. I really appreciate the effort. The discussion at least made me think through some possibilities.7.7KViews0likes0CommentsRe: Unable to load https wsdl
Sorry, Rich. I was trying to avoid unnecessary details so the problem was clear, but it seems I withheld too much. My organization hosts many web services. Rather than having to e-mail the WSDLs and XSDs to those who want to build clients for these services, we enabled the "?wsdl" feature within those services so all folks need is the web service endpoint and then they can pull down the necessary information themselves; however, since the server enforces https, people reported they were unable to create SoapUI projects as I've described, so I tried it myself and confirmed the issue. Once they have the XSD(s) (via e-mail or whatever), they are able to build their web service clients and they work fine. But while building these clients, it's common for people to use SoapUI for comprehension and troubleshooting. And SoapUI's New SOAP Project functionality can't create a new project based on a WSDL URL using the https protocol, as it tries to load the associated XSDs using the http protocol and fails. Perhaps this is just a SoapUI bug, but if there's a SoapUI setting that will get around it, or if there's some change I can make to the WSDLs that will make SoapUI behave, I'd like to know. The particular web service I tested just has the 1 related XSD file, and as shown previously, the include location in the WSDL is just the XSD's filename, as the XSD and the WSDL are in the same folder, so there are no absolute URLs (with protocol, etc.) in the WSDL (other than all the namespaces, which don't count). That leads me to believe it might be a SoapUI bug, but if it is, my Google searches haven't found anyone else mentioning it.8.9KViews0likes2CommentsRe: Unable to load https wsdl
It appears their solution in stackoverflow involves pulling the files down locally. I could ask our clients to manually download the WSDL file and the XSD (or I could just provide these files to them in an e-mail) and then create their SoapUI test projects from the local copies, but of course it's preferable if I could get the New SOAP Project From WSDL feature in SoapUI to behave as expected so clients can set up SoapUI projects, or get WSDL and schema updates in existing projects, on their own.8.8KViews0likes4CommentsRe: Unable to load https wsdl
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.8KViews0likes0CommentsUnable 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.Solved11KViews0likes10Comments