Forum Discussion

flazzes's avatar
flazzes
New Contributor
11 years ago

[Resolved] Error loading WSDL via http/https protocol

Hello.
I've been using soapUI for years, and it's great to test webservices.

Some months ago i've upgraded to Windows 8, and also with the latest version of soapUI there's no way to retrieve the wsdl via http/https protocol nor sending a request (having imported the webservice from a local file).
I googled for weeks for a solutions, and I've already tryed to disable proxy and IPv6 protocol on my machine. Running soapUI as Administrator makes no changes.

Webservices that I tryed to use works perfectly on a Virtual Machine running Windows 7. Those are written in Lotus Domino, SAP and PHP, nothing in particular.

When I create a new project loading the WSDL from a http/https location I always get:

Error loading [url]: java.lang.Exception: Failed to load url;
[url], 0 -

The soapUI log contains these lines:

Fri Nov 15 16:39:11 CET 2013:DEBUG:Getting wsdl component from [url]
Fri Nov 15 16:39:13 CET 2013:ERROR:Failed to load url [url]
Fri Nov 15 16:39:13 CET 2013:ERROR:An error occurred [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException], see error log for details

The error.log contains these lines:

Fri Nov 15 16:39:13 CET 2013:ERROR:com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:138)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:535)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:524)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:236)
at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149)
at java.lang.Thread.run(Unknown Source)

Tryed today with 4.6.1.
Is there anything I can do to make soapUI work?

4 Replies

Sort By
  • flazzes's avatar
    flazzes
    New Contributor
    11 years ago
    Hello mrJames.
    Thank you for your response.

    I already tryed every suggestion written in that page.
    The only thing that works is, as i wrote before, importing the wsdl locally. But, there's not way to fire a request. I think that importing the wsdl via http/https and sending soap requests fail because of the same problem. So even if i can import a wsdl, because it's on local, it makes soapUI unuseful as well.
  • euphoria's avatar
    euphoria
    New Contributor
    11 years ago
    Hi,

    I am having the same problem. Have used soapUI for a long time now with an established web service, yet today I made a couple of changes and none of the definitions on my projects will update (even if I revert all changes). I am getting the same error:

    Mon Nov 18 16:37:49 GMT 2013:DEBUG:Getting wsdl component from [http://localhost:8080/tpService.wsdl]
    Mon Nov 18 16:37:49 GMT 2013:ERROR:Failed to load url [http://localhost:8080/tpService.wsdl]
    Mon Nov 18 16:37:49 GMT 2013:ERROR:An error occurred [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException], see error log for details
    Mon Nov 18 16:37:51 GMT 2013:ERROR:An error occurred [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException], see error log for details
    Mon Nov 18 16:42:12 GMT 2013:ERROR:Failed to load url [file:\F:\Uniform-topicplusSOAP\www\docs\tpService.wsdl]
    Mon Nov 18 16:42:12 GMT 2013:ERROR:An error occurred [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException], see error log for details


    Mon Nov 18 16:42:12 GMT 2013:ERROR:com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
       com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
        at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:138)
        at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:535)
        at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:524)
        at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97)
        at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:236)
        at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
        at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149)
        at java.lang.Thread.run(Unknown Source)


    Have trawled the forums & net and tried various things alas nothing works The web server I am testing against is local and I can happily access the wsdl via http.

    Tried:

    Reverting all changes to the wsdl
    Updating 4.5.1 to 4.6.1 32 bit
    Uninstalling 4.6.1 and installing 64 bit version.
    No proxy enabled
    ipv6 disabled
  • euphoria's avatar
    euphoria
    New Contributor
    11 years ago
    Scrap that, managed to fix it. Found some errors in the wsdl file that once fixed resolved the issue (simple typos). These errors must have been in there for a while so perhaps soapUI is now more sensitive?

    It is a shame the errors being produced are not more useful. I used the WS-I Compliance tool to find one of the errors and created a new project (importing the wsdl afresh) to find the other.

    Sorry for the mis-fired post