Forum Discussion

KwaXi's avatar
KwaXi
New Contributor
13 years ago

Problem with complex types in WSDL

Hello, I've a WSDL with the following types: <wsdl:types> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://service/" elementFormDefault="unqualified" targetNamespace=...
KwaXi's avatar
KwaXi
New Contributor
13 years ago
I forgot to provide the request soapUI produces and the response the webservice generates:

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://service/">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:newMainCheckTableEntity>
         <ser:entity>
            <date>2013.01.23 00:00:00</date>
            <1>service</1>
            <2>profile</2>
            <3>localhost</3>
            <4>profile</4>
            <5>profile</5>
            <6>true</7>
            <7>soapUI</7>
            <8>soapUI</8>
         </ser:entity>
      </ser:newMainCheckTableEntity>
   </soapenv:Body>
</soapenv:Envelope>


Response:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Client</faultcode>
         <faultstring>Unmarshalling Error: unerwartetes Element (URI:"http://service/", lokal:"entity"). Erwartete Elemente sind &lt;{}entity></faultstring>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>


I wrote simple Client using Apache CXF which works flawlessly also some other tools do not have any problems with the WSDL as it is.

Anybody who had similar problems with soapUI and found a solution or is this simply a bug in soapUI?