From the author of

From the author of

Previous articles in this series have described UDDI technology and how to
use the C# .NET and Java APIs for registering services (called
publishing) or finding information about published services (called
inquiry) with UDDI. This article focuses on inquiry with the UDDI4J APIs
in Java and concludes the foundational API-level discussion on UDDI.

NOTE

If you have read the three previous articles in this series, you might want
to skip over or just skim through the following quick refresher and go directly
to the section "UDDI4J APIs."

Quick Review of UDDI

Universal Description, Discovery, and Integration (UDDI) is a registry in
which business entities, the services they offer, and the interfaces (tModels)
for those services can be registered by potential service providers. A UDDI
registry can be thought of as a directory in which "white pages"
contain the business contact information and "yellow pages" contain
the categorized information about services offered by various businesses. UDDI
also contains "green pages" that describe the service interaction
interfaces. Service consumers can use these "pages" to discover the
registered resources and use them as needed.

Interaction with a UDDI registry falls into two categories: publishing
and inquiry. All the UDDI APIs can be classified into these categories.
The communication points of the UDDI registry are also associated with these two
categories: publish URL and inquiry URL. These URLs receive and
process corresponding UDDI API calls.

As noted in the previous articles in this series, the UDDI specification has
undergone several revisions. Version 3 is the most recent specification, but
most of the current implementations of UDDI in production still implement
Version 2. This article therefore focuses on the APIs related to Version 2 of
the specification.