paulprogrammer
13 years agoNew Contributor
WSDL fails to load: how can i get better logs?
Hi All,
I'm trying SoapUI for the second time. When I try to create a new project from our WSDL, I get a dialog that says
The soapui log is also not informative:
Is there any way to boost the logging to find out what resources are invalid?
Some minor notes:
Note that this WSDL does validate, parse, load and generate code using our other tools, so I assume this is an issue with how I'm using SoapUI.
Thanks!
I'm trying SoapUI for the second time. When I try to create a new project from our WSDL, I get a dialog that says
Error loading [https://{mumble}?wsdl]: java.lang.Exception: Failed to load url; https://{mumble}?wsdl, 0 The soapui log is also not informative:
2013-06-03 10:07:30,612 WARN [errorlog] Failed to delete temporary project file; C:\Users\paulwill\Documents\{mumble}\project-temp-9102235176726310796.xml
2013-06-03 10:07:32,634 ERROR [errorlog] 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)Is there any way to boost the logging to find out what resources are invalid?
Some minor notes:
- The server certificate is a snake oil certificate.
- I am behind a proxy server, but shouldn't need access to the internet (unless soapui is trying to download the .xsd for wsdl or something); but I think I have the proxy correctly configured anyway.
Note that this WSDL does validate, parse, load and generate code using our other tools, so I assume this is an issue with how I'm using SoapUI.
Thanks!
