Cannot Create new SoapUI Project from a wsdl that binds ok in CICS WS on mainframe
I'm trying to create a new SoapUI project from a wsdl and xsd that bind ok on mainframe to create a CICS WebService so cannot imagine any syntax error or the like.
Please note I've tried this in SoapUI v5.4.0 & v5.2.1 (NOT SoapUI Pro).
The popup message states;
Error loading [http://localhost/var/cics/msp/dev10/DataContracts/Include/Generic.xsd]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Reference to undefined entity: raquo
The pertinent bit of error log is below, but not particularly useful to me as I cannot determine what is wrong.
2019-11-25 14:26:44,477 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.makeInvalidDefinitionException(WsdlLoader.java:127)
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:117)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:486)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.selectDefinitionParts(SchemaUtils.java:513)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:496)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.selectDefinitionParts(SchemaUtils.java:513)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:496)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:475)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:92)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:208)
at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:131)
at java.lang.Thread.run(Unknown Source)
Any and all suggestions as to what is wrong will be gratefully received.
- Hey MickH,
Yeah, my immediate thought was that the file was malformed (so wont open in a browser or anything with an xml parser), but the error message indicates different.
Did i understand correctly....the .xsd is embedded in the .wsdl?
In that case if you open the .wsdl in any text editor (if youve got xmlspy thats even better as it has an xmlparser included) and search for the ampersand character.
There should be an entity placeholder that isnt one of the five allowed entities (& or > or
< or ' or " which corresponds to & or > or < or ' or ")
There should be another entity value starting with the ampersand character (i.e. '&') that isn't one of the five allowed. That'll be the problem and you need to encode or remove.
Nice one,
Rich Many thanks for all your responses on this subject, particularly Rich. I'm going to mark this as solved, despite the problem still existing. What I did for a workaround was port the xsd & wsdl back to my C: drive, changed the encoding back to UTF and the pathnames to C: and offered that to SoapUI. Of course it worked and so I can progress with a litlle testing.
For now the character set translation problem remains unsolved for this particular wsdl, but I do think it is a SoapUI problem given the EBCDIC version binds perfectly in CICS.
Thanks again.
