Contributions
Re: Cannot Create new SoapUI Project from a wsdl that binds ok in CICS WS on mainframe
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.2.7KViews0likes0CommentsRe: Cannot Create new SoapUI Project from a wsdl that binds ok in CICS WS on mainframe
hi Richie, many thanks for looking at this, it's a real peculiar one. I suspect it has something to do with codeset translation but unfortunately I do not have anything to find offending characters on the mainframe. Please allow me to explain the development process. The object is to get a formed wsdl and xsd onto the unix box where CICS binds them into a CICS Webservice (under the name of the xsd). This part works absolutely fine the steps being; i) Develop on the pc in Visual Studio Code (<?xml version="1.0" encoding="UTF-8"?>) ii) Transfer components to mainframe and change codeset 1st line to <?xml version="1.0" encoding="EBCDIC-CP-US" standalone="no"?> iii) Transfer to Unix machine and get CICS WS to bind the members. All good so far. In order to test the Webservice, I browse the unix wsdl in Internet Explorer and offer the address in IE to create a new SoapUI project. It is at this point that I encounter the SoapUI problem. This is a tried and tested method of testing the wsdl's and works for all other examples. So, can I assume that there is some 'dodgy' character in the Unix version of the constructs that SoapUI does not like? TIA2.8KViews0likes2CommentsRe: Cannot Create new SoapUI Project from a wsdl that binds ok in CICS WS on mainframe
Thanks for the replies thus far. Yes, the wsdl opens fine in Internet Explorer. I then can port it to mainframe and bind it into a CICS Webservice so syntactically the wsdl and associated xsdis fine. I think Richie has touched upon the real problem in that SoapUI is objecting to some form of non-displayable character/s. However, I cannot see these in Visual Studio Code and do not know how to view / find these. Any further suggestions along these lines would be helpful. TIA2.8KViews0likes4CommentsCannot 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 andxsd 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.Solved2.9KViews0likes7Comments