The first article in this series discussed creating your own UDDI registry, while this article discusses how to access that registry from a client application. What do you see as the future of this technology? Is it useful now? Will it be useful in the future, or is UDDI simply the opening salvo in an ongoing struggle to automate knowledge discovery? Did the articles meet your needs? Let us know in the DevX Java discussion forum.
Build a Client Application to Access a UDDI Registry
Now that you've seen how to set up a UDDI registry on your server, it's time to learn how to use it from a client application.
by Jeff Hanson
July 20, 2004
n the first article in this series, you saw how the Universal Description, Discovery, and Integration (UDDI) specification and protocol work together to define messages, application programming interfaces (APIs), and data structures for building distributed registries of Web services. You also saw how to store the business and technical information associated with these services. See the sidebar on this page for a review of UDDI's high-level architecture.
In this article, you'll see how to build a client application that uses your UDDI registry to locate businesses and services stored there, how to anticipate and handle some common errors, and how to understand some standard details about UDDI SOAP messages.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
n the 
