> Worst case -- use the low-level API and generate the messages manually. In my experience with perl soap stacks, that has been the "best case".
-D -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, April 15, 2005 8:29 AM To: axis-user@ws.apache.org Subject: Re: R: Ok with VB.NET, Axis & Office VBA clients, error in SOAP:Perl...WSDL problem? SOAP::Lite is generating a message that does not conform to the WSDL. I'm not familiar with SOAP::Lite, but I've seen other questions from users regarding these dynamically generated element names ("c-gensym3"), which are totally inappropriate. I'm sure there must be a way to get Perl to generate SOAP messages that conform to the WSDL. Worst case -- use the low-level API and generate the messages manually. Anne
