Amended SoapClient.lookupComplexType to work with a valid WSDL. In my fi...

[notatestuser]

...le, an 'element' tag had the 'name' attribute containing the name of the type, whereby 'complexType' was a child containing its sequence of parameters. I've amended the XPath query to work with both structures as I assume [the creator] hasn't done it wrongly intentionally and your own WSDL might actually be formed the other way.

Here's a relevant snippet from my own WSDL that exhibits the disparity:

<element name="getLostUsername">
<complexType>
<sequence>
<element name="firstname" nillable="true" type="xsd:string"/>
<element name="lastname" nillable="true" type="xsd:string"/>
<element name="dateofbirth" nillable="true" type="xsd:string"/>
<element name="placeofbirth" nillable="true" type="xsd:string"/>
<element name="realm" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</element>

...and it seems yours might have looked something like:

<complexType name="getLostUsername">
<sequence>
...

Nonetheless, it'll now work with both.