I have two WSDL files that wsdl2perl.pl generates errors on.

One is from Lyris ListManager v8.95 from a TCL based service available at http://topaz1.mail.cornell.edu/lmapi895.wsdl

The other is from Lyris ListManager v10.3c based on gSOAP v2.7.7 available at http://topaz1.mail.cornell.edu/lmapi103.wsdl

Both of them cause wsdl2perl.pl (from SOAP::WSDL v2.00.10 using perl 5.10.1) to die with 'no node' errors, likely because wsdl2perl.pl does not understand {http://schemas.xmlsoap.org/wsdl/}arrayType

typescripts of these executions are available at

http://topaz1.mail.cornell.edu/lmapi895.wsdl.out.txt

http://topaz1.mail.cornell.edu/lmapi103.wsdl.out.txt

I'm trying to build a client to work with these services ... I don't have source for the server hence my ability to change the WSDL is limited

What can I do to make this work? Perhaps light edits to the WSDL files? Some sort of 'fix' to SOAP::WSDL ?

1) SOAP::Lite can process both these files

1a) and works fine as a client with the v8.95 service

1b) yet fails as a client with the v10.3 service (likely because there are 2 schema's defined)

2) XML::Compile can't handle them because they are rpc/encoded

3) unfortunately I must upgrade to the v10.3

QUESTION: Is there an essay somewhere that promotes the document/literal style over the rpc/encoded style? That would be a useful tool for me in encouraging the vendor to change their WSDL. Note the vendor seems to desire interoperating with .NET

Regards,