There's no need to do this.
In an rpc/encoded WSDL, the message part must reference a type, not an
element. It's perfectly legal to reference an xsd type. So the
original WSDL description is fine:
The error was caused by the erroneously placed soapAction attri
Christian,
I think the type for the part name (nameParam) must refer to an element
(or complex type) defined in your schema type, not a xsd:string.
Refering to message:
Change the type to an element in the wsdlns namespace, and you shouldn't
get the error.
As
