Forum Discussion

MickH's avatar
MickH
New Contributor
5 years ago
Solved

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 Soa...
  • richie's avatar
    richie
    5 years ago
    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
    &lt; or &apos; or &quot; 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
  • MickH's avatar
    MickH
    5 years ago

    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.

nmrao's avatar
nmrao
Champion Level 3
5 years ago
Please try opening the wsdl from browser and see if that is ok or do you see any error.
  • MickH's avatar
    MickH
    New Contributor
    5 years ago

    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 xsd is 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.

     

    TIA

     

    • richie's avatar
      richie
      Community Hero
      5 years ago
      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 (&amp; or &gt; or
      &lt; or &apos; or &quot; 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
      • MickH's avatar
        MickH
        New Contributor
        5 years ago

        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? TIA