Constructing a UDDI Client, Calling the UDDI Registry (cont.)

The UDDI Registry Replies
The response from the UDDI registry is the XML structure BusinessList, which contains a list of businesses matching the search criteria. Listing 4 shows a sample BusinessList structure. The BusinessList parses and processes the XML structure returned by UDDI.

The root tag <BusinessList> contains information about the UDDI operator, namespace, and version of the UDDI API. It also contains multiple BusinessInfo elements. Each <BusinessInfo> element represents one business and contains a name, a description, and a BusinessKey. Name is simply name of the business, description is some text describing the business, and BusinessKey uniquely identifies the business. Each BusinessInfo structure contains multiple <ServiceInfo> elements, each of which represent one service that a business provides.

The constructor in the BusinessList class takes the complete BusinessList XML string and populates its internal structures using KXML. Once populated, all the information about a BusinessList class is available through public Get methods. Users of this class can also get information about individual BusinessInfo elements and their children, the ServiceInfo elements.

That completes the implementation of the find_business method. If you want to perform drill-down searching, this sample implementation of the find_business method can be used as an architectural model to implement a complete UDDI client in Java.

UDDI has provided comprehensive means to search for specific Web services at a UDDI registry. Once users have discovered them, they'll want to explore further details of those services. My article "Using UDDI as a Search Engine" covers how to use different methods in UDDI APIs that lead to the discovery of WSDL file URLs, which disclose more information about registered services (see "Designing a WSDL Client").

Bilal Siddiqui is an Electronics Engineer, an XML consultant, and the co-founder of WaxSys, a company focused on simplifying e-Business. He is a technology evangelist and frequently published technical author. You can contact Bilal at bsiddiqui@waxsys.com.

Resources for this Article
W3C WDSL Specifications
W3C SOAP Specifications
kXML from Enhydra.org
Good Overview Article on SOAP from Sun
PerfectXML.com: Good Tutorials and Articles
An Interesting Open Source Java-based Implementation of a UDDI Registry
Using UDDI as a Search Engine
Building Web Services with Java: Making Sense of XML, SOAP, WSDL and UDDI from SAMS


Back to the Introduction

In this Article
Introduction Implementing UDDI's Find Qualifiers
The UDDI Client The UDDI Registry Replies
 





FEATURE SOFTWARE:
dtSearch Web
Add power searching to your web site.
Buy Now!

Encrypt It
Encrypt and Decrypt Data, Passwords and Files within your application.
Buy Now!

Standards Organizations and Web Service Coalitions

Key Platforms

Pure-Play Web Services Vendors

Web Service Technologies or Components

From Sun.com

For Further Reading

Discussion Groups
Java Web Services
.NET Web Services

Back to the Special Report

Java Zone

2001 Special Report: Judging Java

TALK BACK
UDDI is a critical part of the "killer app" of XML Web services. Do you think it's too complicated? Will the standard evolve? Will it become simpler? Should Sun support UDDI as an integral component of J2EE, or is it too soon to tell? Do you think the current UDDI implmentation is a victim of committee development? Let us know in the Java Web Services discussion group.


Sponsored Links

Advertising Info  |   Member Services  |   Contact Us  |   Help  |   Feedback  |   Site Map
Jupiterweb networks

internet.comearthweb.comDevx.comClickZ

Search Jupiterweb:

Jupitermedia Corporation has four divisions:
JupiterWeb, JupiterResearch, JupiterEvents, and JupiterImages

Copyright 2004 Jupitermedia Corporation All Rights Reserved.
Legal Notices, Licensing, Reprints, & Permissions, Privacy Policy.

Jupitermedia Corporate Info | Newsletters | Tech Jobs | E-mail Offers

Copyright Information/Privacy Statement