The UDDI (Universal Description, Discovery and Integration) Project is a comprehensive, open industry initiative enabling businesses to (I) discover each other, and (II) define how they interact over the internet and share information in a global registry architecture. UDDI is the building block which will enable businesses to quickly, easily and dynamically find and transact with one another via their preferred applications.
UDDI4J is a Java class library that provides an API that is can be used to interact with a UDDI registry. This class library generates and parses messages sent to and received from a UDDI server.
The central class in this set of APIs is com.ibm.uddi.client.UDDIProxy. It is a proxy for the UDDI server that is accessed from client code. Its methods map to the UDDI Programmer's API Specification.
The classes within com.ibm.uddi.datatype represent data objects used to send or receive UDDI information. and in the, business, service, tmodel subpackages represent data objects that are sent on calls or received from the server.
The subpackage com.ibm.uddi.request contains messages sent to the server. These classes are typically not used directly, rather the UDDIProxy class uses these classes.
Similarly, the subpackage com.ibm.uddi.response represents response messages from a UDDI server.
UDDIException is thrown when errors are received from the UDDI proxy when invoking UDDIProxy inquiry methods. UDDIException can contain a DispositionReport with information about the error.
APIs that do not return a data object return a disposition report directly.
SOAPException is thrown if a communication error occurs or if the resulting data cannot be properly parsed as a valid SOAP message.
Apache SOAP has the following additional prerequisites. Consult the Apache SOAP website for official information regarding prereqs.
ant targetwhere target is one of the following:
A set of samples is provided to illustrate the basics of using the inquiry api, publish api, and error handling.
java FindBusinessExample