Home > Articles > Mobile Application Development & Programming > HTML5 & Web Standards

  • Print
  • + Share This
From the author of


The .NET Framework, announced and championed by Microsoft, provides support for the UDDI initiative. The .NET platform provides the Microsoft UDDI .NET software development kit (SDK), which helps in building UDDI client-side components using the .NET technology. The SDK provides APIs for languages that run in the .NET runtime. The SDK can be downloaded from the Microsoft site and installed in the Visual Studio .NET environment.


Once a reference is added for this SDK in the program, all the classes described below become available to the developer.

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 (most notably, those of Microsoft and IBM). This article therefore focuses on the APIs related to Version 2 of the specification.

To understand the APIs, it's essential to know the possible interactions with a UDDI registry.

UDDI Interaction Patterns

To demonstrate the use of the C# and Java APIs, let's walk through the business case of a service provider that wants to publish its service within the Universal Business Registry (UBR), a global pool of UDDI registries. Figure 2 depicts typical patterns associated with UDDI registry interaction.

Figure 2Figure 2 Typical interaction patterns with a UDDI registry.

Interaction with a UDDI registry via its communication points 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.

  • + Share This
  • 🔖 Save To Your Account