Forum Discussion

dham79's avatar
13 years ago

java.io.IOException when loading WSDL

Hello everybody

I am trying to set up a new project (soapUI 4.5.1) and load a WSDL like this:

http://localhost:8280/services/OfferteProxy?wsdl

The WSDL contains a schemaLocation as follows:

schemaLocation="OfferteProxy?xsd=http://external:7865/ServiceImpl/online?xsd=1.xsd"

(this is a proxy web service generated with WSO2 ESB)

soapUI is not able to load the XSD. The error is

Error loading [OfferteProxy?xsd=http://external:7865/ServiceImpl/online?xsd=1.xsd]: java.io.IOException: Attempted read from closed stream

In the soapUI log, it says

ERROR:Failed to load url [OfferteProxy?xsd=http://external:7865/ServiceImpl/online?xsd=1.xsd]
ERROR:An error occured [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException], see error log for details

and the error log says

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.selectDefinitionParts(SchemaUtils.java:565)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:545)
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:226)
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)


So I guess the URL to the XSD is wrong, however, this URL

http://localhost:8280/services/OfferteProxy?xsd=http://external:7865/ServiceImpl/online?xsd=1.xsd


is working in a browser and returning the correct XSD.

Does anyone have an idea why soapUI is not able to load the XSD? Maybe because of the strange URL (which was generated from the WSO2 proxy web service)? Could this be a bug in soapUI?

Thanks in advance for any advice.
No RepliesBe the first to reply