This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
Besides these tags, inquiry imports the combined lists from find and get, while
publish returns the combination of auth, delete, save, and validate. As with most
modules that export, the special tag
all pulls in the complete set.
The class uses the same style and syntax for error handling (
on_fault) and debug-
SOAP::Trace facility) as the previous classes.
As with the SOAP::Data class from which this derives, the purpose of UDDI::Data is to
provide explicit typing and namespace control over values that the application is
passing to other methods. The usage and style are identical to
UDDI::Lite, this class exports a large number of names that can be used as
shortcuts in creating structures for a UDDI message. The names are identical to the
UDDI element names as defined in the schema for UDDI. There are too many to list
here, but the distribution includes some examples in the manpage, as well as some
The UDDI::SOM package is identical to SOAP::SOM, except that it overrides the result
method to use an XPath expression specific to UDDI responses.
UDDI::Serializer and UDDI::Deserializer
These two classes are derived from their SOAP counterparts, with UDDI-specific
functionality added. Given the much more strictly defined nature of UDDI syntax,
neither class is recommended for subclassing or replacement on the
Table B-1. UDDI::Lite importable functions (continued)
Import tag Functions