This section provides a tutorial example on how to use the SOAP::Data class to build the request parameter element with correct element name and a namespace. My first SOAP::Lite program works now with the GetSpeech Web service.
By reading the manual, SOAP::Lite 0.710 seems to be quite different than SOAP::Lite 0.55:
Package name has been changed to "SOAP::Lite - Perl's Web Services Toolkit"
from "SOAP::Lite - Client and server side SOAP implementation".
Old uri() function is deprecated. ns() or default_ns() should be used instead of uri().
New soapversion() function is introduced to support SOAP 1.2.
New send_receive() function is introduced to support generic SOAP messages.
SOAP::Lite features support for the SOAP with Attachments specification now.
SOAP::Lite 0.710 manual also gives example codes to support 4 different SOAP message styles:
rpc/encoded - Typed, positional parameters.
Widely used in scripting languages. The type of the arguments is included in the message.
Arrays and the like may be encoded using SOAP encoding rules (or others).
rpc/literal - As-is, positional parameters. The type of arguments is
defined by some pre-exchanged interface definition.
document/encoded - Specified message with typed elements. Rarely used.
document/literal - Specified message with as-is elements.
The message specification and element types are defined by some pre-exchanged interface definition.
Becoming the predominant SOAP message style.
