This class has no methods or objects.
It is used only to manage and manipulate the runtime tracing of execution within the toolkit.
In absence of methods,
this section reviews the events that may be configured and the ways of configuring them.

Tracing is enabled by the SOAP::Lite import method.
This is usually done at compile-time,
though it may be done explicitly by calling import directly.
The commands for setting up tracing start with the keyword +trace.
Alternately,
+debug may be used; the two are interchangeable.
After the initial keyword,
one or more of the signals detailed here may be specified,
optionally with a callback to handle them.
When specifying multiple signals to be handled by a single callback,
it is sufficient to list all of them first,
followed finally by the callback,
as in:

In the fragment, the reference to message_level is installed as the callback for both method and fault signals, while lower_level is installed for trace and object events. If callbacks aren't explicitly provided, the default tracing action is to log a message to Perl's STDOUT file descriptor. Callbacks should expect a one or more arguments passed in, though the nature of the arguments varies based on the signal.

Any signal can be disabled by prefacing the name with a hyphen, such as -result. This is useful with the pseudosignal "all," which is shorthand for the full list of signals. The following fragment disables only the two signals, while still enabling the rest:

SOAP::Lite->import(+trace => all => -result => -parameters);

If the keyword +trace (or +debug) is used without any signals specified, it enables all signals (as if all were implied).

The signals and their meaning follow. Each also bears a note as to whether the signal is relevant to a server application, client application, or both.

Triggered in the transport layer just before a request is sent and immediately after a response is received. Each time the signal is sent, the sole argument to the callback is the relevant object. On requests, this is a HTTP::Request object; for responses, it's a HTTP::Response object.

Triggered before a method call is actually dispatched, with the data that is intended for the call itself. The parameters for the method call are passed in as a list, after having been deserialized into Perl data.

Like the two previous, this signal is triggered when the method SOAP::Serializer::envelope is called with an initial parameter of freeform. This syntax is used when the method is creating SOAP::Data objects from free-form input data.

Triggered at the entry-point of many of the more-significant functions. Not all the functions within the SOAP::Lite classes trigger this signal. Those that do are primarily the highly visible functions described in the interface descriptions for the various classes.

You can disable tracing for a set of signals by prefixing the signal name with a hyphen. Therefore, if you wish to enable tracing for every signal EXCEPT transport signals, then you would use the code below:

You can optionally provide a subroutine or callback to each signal trace you declare. Each time a signal is received, it is passed to the corresponding subroutine. For example, the following code effectively logs all fault signals to a file called fault.log:

The transport signal is unique in the that the signal is not a text string, but the actually HTTP::Request being sent (just prior to be sent), or HTTP::Response object (immediately after it was received). The following code sample shows how to make use of this:

Special thanks to O'Reilly publishing which has graciously allowed SOAP::Lite to republish and redistribute large excerpts from Programming Web Services with Perl, mainly the SOAP::Lite reference found in Appendix B.