Nil bugfix

[jasa80]

If a complex type element is defined as nillable in SOAP xsd e.g.:

<xs:element name="parent" nillable="true" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="child1" type="xs:string"/>
      <xs:element name="child2" type="xs:string" minOccurs="0"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

Now if we try to define the parent as Nil to get the following output for it:
<ns:parent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>

The result however with current implementation is:

<ns:parent>
  <ns:child1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
</ns:parent>

So it seems to set the first child element as Nil although it should be done for the parent.