in reply to SOAP::Lite and SOAP::WSDL

The 'uri' in SOAP::Lite is not the same as the service descriptor (which is called with 'service'). SOAP::WSDL needs to be pointed at a WSDL document, which is an XML document that describes the calling and return syntax of a webservice.

The URI for a SOAP call is just an identifier, and doesn't need to actually resolve to a document. (which in this particular case, it doesn't.) Ideally, when you have a WSDL document, you don't need to specify the URI or proxy, as they're already defined within the service description.

Also, as I mentioned before, SOAP::WSDL was written because of lacking WSDL support in SOAP::Lite -- SOAP::Lite has since been improved, and SOAP::WSDL isn't being maintained, so I don't know how beneficial it is to use SOAP::WSDL.

Replies are listed 'Best First'.
Re^2: SOAP::Lite and SOAP::WSDL
by mrguy123 (Hermit) on Jul 24, 2006 at 15:48 UTC
    Thanks, that's very helpful advice about SOAP::WSDL. While we're on the subject, I understand from the documentation that one of SOAP::WSDL's greatest advantages over SOAP::Lite is that you can send the parameters in a hash. I didn't see anything similar in SOAP::Lite, and because I want to send a generic data structure in the SOAP request due to inheritence, the ability to use a hash was one of my main reasons to want to use SOAP::WSDL. Do you know if I can send a hash or something similar in SOAP::Lite? I am also posting these questions in the SOAP::Lite newsgroup due to your previous advice.
    Thanks again, Guy