I want the list of UDDI registry providers and their features and comparisons. Can somebody help me in this?
I know that IBM, MS provider UDDI registries. But I want to know the features of those as well.
Here is an excerpt from my article "Whatever happened to X"
It turns out that, although UDDI is still part of Web Services Interoperability (WS-I) standards, the envisioned big public registries never evolved and the major players such as IBM closed their public example UDDI services. Instead, UDDI is alive and well inside private corporate networks for service-oriented architecture (SOA) and has wide toolkit support in commercial and open source toolkits
The original vision of big public registries never happened. Instead people are finding services with other methods and depending on WSDL to get the service details.
With regard to public UDDI registry, I understand what you have told.
I am trying to understand the UDDI registry. I have few doubts. I will be happy if you can calrify me on these (My doubts might be very basic and simple, but I am novice to Web Services as well Ranch )
1. Please validate if my understanding is right : B2B automation did not found to be success. Hence, a public UDDI Business Registy is no more required, as the consumer would always communicate with the provider to automate the B2B. Hence, the consumer can get the description of the Web Service either from the provider's UDDI registry or the provider can provide the URI of the wsdl to the consumer to access.
If this understanding is right, can you tell me why do we still need to have the information about the service provider? Would the Service implementation and metadata information not do?
2. There are list of vendors who provider UDDI registry servers. Now how do I decide upon the UDDI registry and what is DE feature that decides the UDDI registry server?
An alternative to using an UDDI registry is to use the JAX-WS supported OASIS XML Catalogs 1.1.
This way URIs of WSDL and XML schemas can be mapped to, for instance, a servlet running in a Tomcat instance.
The servlet can be very simple, just returning the WSDL or XML schema currently configured for the URI, or more advanced, for instance selecting between several instances of the same service and returning a WSDL accordingly etc etc.