Forum Discussion

Valkenswaard's avatar
Valkenswaard
New Contributor
13 years ago

Tab Forms and arrays

Hello ,

In the Wsdl that is published by my Delphi-server the following XML-code is generated:
      <xs:complexType name="Array_Of_Afdeling">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:Afdeling[]" xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="Afdeling">
        <xs:sequence>
          <xs:element name="Kode" type="xs:string"/>
          <xs:element name="Naam" type="xs:string"/>
        </xs:sequence>
      </xs:complexType>

I want to pass this array in a request message. My trial version of SoapUI PRO 4.5.0 has a tab ‘Form’ for Requests, that provides me with special buttons to add/delete/clear items to this array. But however, the array that is presented to me on the tab 'Form' is a mess and useless. It is mixed up with other elements of the request.

When I change this generated part to 

     <xs:complexType name="Array_Of_Afdeling">
          <xs:sequence>
         <xs:element name="Afdelingen" type="s1:Afdeling" minOccurs="0" maxOccurs="unbounded"/>
          <xs:sequence>
      </xs:complexType>
      <xs:complexType name="Afdeling">
        <xs:sequence>
          <xs:element name="Kode" type="xs:string"/>
          <xs:element name="Naam" type="xs:string"/>
        </xs:sequence>
      </xs:complexType>

the tab "Forms' works fine and I can add and delete new items in the array as much as I want.

However I have the feeling that the first part is also correct, but is only handled wrongly by SoapUi. When I use the first part in other tools like Mapforce, the request of operation with this first part can be used with no problems.

Does anyone know if I'm doing something wrong?

Regards, Jan
  • Valkenswaard's avatar
    Valkenswaard
    New Contributor
    13 years ago
    Because nobody reacts on my issue, I show you the strange request, that Soapui makes of this generated XML-code.

    <soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:hcc="http://Hcc" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
       <soapenv:Header/>
       <soapenv:Body>
          <hcc:SetWerkNemer soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
             <Input xsi:type="hcc:Werknemer" xs:type="type:Werknemer" xmlns:xs="http://www.w3.org/2000/XMLSchema-instance">
                <Leeftijd xsi:type="xsd:int" xn:type="http://Hcc" xmlns:xn="http://www.w3.org/2000/xmlns/">?<Kode xn:type="http://www.w3.org/2001/XMLSchema"/><Naam xs:type="type:string"/></Leeftijd>
                <Naam xsi:type="xsd:string" xs:type="type:Afdeling">?<Kode xn:type="http://www.w3.org/2001/XMLSchema" xmlns:xn="http://www.w3.org/2000/xmlns/"/><Naam xs:type="type:string"/></Naam>
                <Afdelingen xsi:type="hcc:Array_Of_Afdeling" soapenc:arrayType="hcc:Afdeling[]" xs:type="type:Afdeling"><Kode xs:type="type:string"/><Naam xs:type="type:string"/></Afdelingen>
             </Input>
          </hcc:SetWerkNemer>
       </soapenv:Body>
    </soapenv:Envelope>

    I hope this will ring a bell to somebody.

    Regards, Jan