| |

Introduction

The "inspireit.uddi.request" package contains two classes used to query an UDDI registry: UDDIQuerier and UDDIQuerierExt . UDDIQuerier is the main class to query information from an UDDI registry. UDDIQuerierExt provides extended querying capabilities. UDDIQuerier implements the UDDI inquiry API defined by the UDDI specification. The name of an UDDIQuerier method always corresponds to the name of the UDDI inquiry it represents. For example, findBusiness is the name of the UDDIQuerier method to perform a find_business call. As a result, a Ruddi developer can directly refer to the UDDI specification in order to get fine-grained details on a UDDIQuerier method.

Working with UDDIQuerier

UDDIQuerier defines a set of methods to format valid UDDI inquiry requests. The most useful as well as the general form of a given inquiry request are always provided. For example, a Ruddi developer can find a business by name by invoking the findBusiness(name) method as well as by invoking the general findBusiness(names, discoveryURLs, identifierBag, categoryBag, tModelBag, findQualifiers, maxRows) method.

As a general rule, it is advised to always use the method whose signature best matches the actual needs. Not only does this allow avoiding a long list of null parameter values in the method invokation, but it better guarantees support for older versions of UDDI. To take back the findBusiness example, the findBusiness(name) method invocation is compatible with all versions of UDDI, while the general form is only available starting from UDDI 2.0. A Ruddi developer can refer to the Javadoc documentation in order to determine the UDDI-level support of the various inquiries.

UDDIQuerier handles the querying capabilities of versions 3.0, 2.0 and 1.0 of UDDI. The Ruddi runtime automatically formats the UDDI inquiry requests in compliance with the targeted UDDI version. Methods that reflect inquiries that are not possible being given a specific UDDI version throw a java.lang.Runtime exception.

UDDIQuerier provides two types of methods: methods returning a response object and methods returning an UDDIInputStream . Methods returning a response object allow accessing UDDI registry replies in a high-level manner. Methods returning an UDDIInputStream can be used, for example, in the context of an XSLT transformation of an UDDI registry reply. This approach allows avoiding the overhead of intermediate object creation. It is to be noticed that the UDDIInputStream class comes with methods allowing reading high-level response objects from an InputStream .

Working with UDDIQuerierExt

UDDIQuerierExt provides extended querying capabilities that are typically handled by the Ruddi runtime by a dialogue composed of several request/response interactions. UDDIQuerierExt is compatible with any regular UDDI registry. Working with UDDIQuerierExt is similar to working with UDDIQuerier .