| |

Introduction

The "inspireit.uddi.request" package contains one class used to publish to an UDDI registry: UDDIPublisher . UDDIPublisher implements the UDDI publishing API defined by the UDDI specification. The name of an UDDIPublisher method always corresponds to the name of the UDDI publishing request it represents. For example, deleteBusiness is the name of the UDDIPublisher method to perform a delete_business call. As a result, a Ruddi developer can directly refer to the UDDI specification in order to get fine-grained details on a UDDIPublisher method.

Working with UDDIPublisher

UDDIPublisher defines a set of methods to format valid UDDI publishing requests. The most useful as well as the general form of a given publishing request are always provided. For example, a Ruddi developer can delete a specific binding by invoking the deleteBinding(bindingKey) method as well as by invoking the general deleteBinging(bindingKeys) method.

UDDIPublisher handles the publishing capabilities of versions 3.0, 2.0 and 1.0 of UDDI. The Ruddi runtime automatically formats the UDDI publishing requests in compliance with the targeted UDDI version. Methods that reflect publishing requests that are not possible being given a specific UDDI version throw a java.lang.Runtime exception. A Ruddi developer can refer to the Javadoc documentation in order to determine the UDDI-level support of the various publishing requests.

Contrarily to UDDIQuerier , UDDIPublisher only provides one type of method returning UDDI registry response objects. It was indeed felt that the ability to directly access the UDDI registry response stream was of low interest in the context of publishing.