NAME

NOTICE

This module has a large number of known bugs and is not being actively developed. This 3.0 release is intended to update the module to pass tests on newer Perls. This is a service to existing applications already dependent on this module.

You'll need a MyPersonClass module in your search path for this to work - see SOAP::WSDL::XSD::ComplexType on how to build / generate one.

servicename

$soap->servicename('Name');

Sets the service to operate on. If no service is set via servicename, the first service found is used.

Returns the soap object, so you can chain calls like

$soap->servicename->('Name')->portname('Port');

portname

$soap->portname('Name');

Sets the port to operate on. If no port is set via portname, the first port found is used.

Returns the soap object, so you can chain calls like

$soap->portname('Port')->call('MyMethod', %data);

no_dispatch

When set, call() returns the plain request XML instead of dispatching the SOAP call to the SOAP service. Handy for testing/debugging.

ACCESS TO SOAP::WSDL's internals

get_client / set_client

Returns the SOAP client implementation used (normally a SOAP::WSDL::Client object).

EXAMPLES

See the examples/ directory.

Differences to previous versions

WSDL handling

SOAP::WSDL 2 is a complete rewrite. While SOAP::WSDL 1.x attempted to process the WSDL file on the fly by using XPath queries, SOAP:WSDL 2 uses a Expat handler for parsing the WSDL and building up a object tree representing it's content.

The object tree has two main functions: It knows how to serialize data passed as hash ref, and how to render the WSDL elements found into perl classes.

call() with no_dispatch set to true now returns the complete SOAP request envelope, not only the body's content.

outputxml

call() with outputxml set to true now returns the complete SOAP response envelope, not only the body's content.

servicename/portname

Both servicename and portname can only be called after calling wsdlinit().

You may pass the servicename and portname as attributes to wsdlinit, though.

Differences to previous versions

The following functionality is no longer supported:

Operation overloading

The SOAP standard allows operation overloading - that is, you may specify SOAP operations with more than one message. The client/server than can choose which message to send. This SOAP feature is usually used similar to the use of methods with different argument lists in C++.

Operation overloading is no longer supported. The WS-I Basic profile does not operation overloading. The same functionality as operation overloading can be obtained by using a choice declaration in the XML Schema.

readable

Readable has no effect any more. If you need readable debug output, copy the SOAP message to your favorite XML editor and run the source format command. Outputting readable XML requires lots of programming for little use: The resulting XMl is still quite unreadable.

on_action

Setting on_action is not required any more, the appropriate value is automatically taken from the WSDL. on_action is a no-op, and is just here for compatibility issues.

Differences to SOAP::Lite

readable

readable is a no-op in SOAP::WSDL. Actually, the XML output from SOAP::Lite is hardly readable, either with readable switched on.

If you need readable XML messages, I suggest using your favorite XML editor for displaying and formatting.

BUGS AND LIMITATIONS

This module is in legacy maintenance mode. Only show stopper bugs are being fixed, until/unless someone wishes to resume active development on it. Scott Walters, scott@slowass.net has obtained co-mainter from the CPAN admins for the purpose of applying existing fixes people have submit to the RT tracker, and to apply other fixes as needed to get the module to install and run on newer Perls. Non show-stopper bugs reports without fixes will be added to this list of limitations. Of course, fixes for these and other bugs are welcome. Scott does not get email from rt.cpan.org, so please drop an email to him at scott@slowass.net if you open a ticket there.

Breaks the idiom $package->can("SUPER::method") in your code

If you redefine UNIVERSAL::can(), and someone tries to do $package->can("SUPER::method"), it'll look at your packages @ISA, not theirs. This module does precicely that, by way of its dependency on Class::Std::Fast.

$obj == undef does not work in perl 5.8.6 and perl 5.8.7

Due to some strange behaviour in perl 5.8.6 and perl 5.8.7, stringification overloading is not triggered during comparison with undef.

While this is probably harmless in most cases, it's important to know that you need to do

defined( $obj->get_value() )

to check for undef values in simpleType objects.

perl 5.8.0 or higher required

SOAP::WSDL needs perl 5.8.0 or higher. This is due to a bug in perls before - see http://aspn.activestate.com/ASPN/Mail/Message/perl5-porters/929746 for details.

Apache SOAP datatypes are not supported

You can't use SOAP::WSDL with Apache SOAP datatypes like map.

Incomplete XML Schema definitions support

This section describes the limitations of SOAP::WSDL, that is the interpreting SOAP client. For limitations of wsdl2perl.pl generated SOAP clients, see SOAP::WSDL::Manual::XSD.

XML Schema attribute definitions are not supported in interpreting mode.

The following XML Schema definitions varieties are not supported in interpreting mod:

group
simpleContent

The following XML Schema definition content model is only partially supported in interpreting mode: