B.4 UDDI::Lite

The UDDI support that SOAP::Lite provides is accomplished through subclassing the basic SOAP components , much as XMLRPC::Lite does to provide the XML-RPC functionality. This section will be less detailed as a result, focusing on the aspects of the methods and class behavior that are different from the parent classes.

B.4.1 UDDI::Lite

The UDDI::Lite class itself is a subclass of SOAP::Lite and inherits all the transport and related functionality from its parent. For the basic utility methods ( new , proxy , etc.) refer back to that section earlier in this appendix. What this class does offer that goes beyond the basic SOAP capability is predefined class methods for the various UDDI elements. Since UDDI has a much stricter grammar than the more generalized SOAP, the class is able to cater to that in the functionality it offers.

The methods are named directly after the UDDI XML element they represent. They are also importable and may be used as normal function calls rather than object methods. Table B-1 lists the methods grouped by the import tag applications can use to get access to them:

Table B-1. UDDI::Lite importable functions

Import tag	Functions
auth	get_authToken discard_authToken get_registeredInfo
delete	delete_binding delete_business delete_service delete_tModel
find	find_binding find_business find_service find_tModel
get	get_bindingDetail get_businessDetail get_businessDetailExt get_serviceDetail get_tModelDetail
save	save_binding save_business save_service save_tModel
validate	validate_categorization

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 debugging (the SOAP::Trace facility) as the previous classes.

B.4.2 UDDI::Data

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 SOAP::Data .

Like 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 example code.

B.4.3 UDDI::SOM

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.

B.4.4 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 UDDI::Lite object.