Java Tutorial - Java Scipt :
Web Service Registries
SOAP standardizes the invocation of Web services. WSDL standardizes the description, explaining how a Web service can be accessed. That still leaves the question of where, which is the problem that Web service registries are meant to solve.
Registry services are necessary for the discovery of Web services. They serve as a directory through which appropriate Web services can be placed and found. Without registries, a lot of effort would be spent on the discovery of Web services. Aregistry standard is important for Web services to scale up to a large audience.
JAXR is an API that abstracts access to a registry. The two registry standards of note are the UDDI Registry and ebXML Registry. The UDDI Registry and ebXML Registry standards differ in the scope of features that are mandated. JAXR uses the concept of level conformance to support the two registry standards.
Level 1 is required by all JAXR implementations and corresponds to the feature set in a UDDI Registry. Meanwhile, Level 2 is optional and defines the interfaces to more advanced features, as in the ebXML standard.
Because Apache Axis does not implement a Web service registry, we won’t cover it in detail. There are some open source projects out there that are working on building registry implementations, including ebXMLRR and jUDDI.
