WAS v8.5 > Develop applications > Develop web services - UDDI registry > Develop with the UDDI registry > Use the JAXR provider for UDDIJava API for XML Registries (JAXR) provider for UDDI
The JAXR is a Java client API for accessing both UDDI (v2 only) and ebXML registries. It is part of the Java EE specification.
Deprecated feature: From WebSphere Application Server v8.0, Java API for XML Registries (JAX-R) APIs are deprecated. The Java EE 6 platform began the deprecation process for JAX-R because it is based on Universal Description, Discovery and Integration (UDDI) 2 technology, which is no longer relevant. If the applications use JAX-R, then you might consider using UDDI 3.
The JAXR API comprises the Java EE packages javax.xml.registry and javax.xml.registry.infomodel. Java EE API documentation is at Web Services Reference.
The preferred UDDI Java client APIs are:
- UDDI4J v2, for UDDI v2
- UDDI v3 Client for Java, for UDDI v3
JAXR provider
The current JAXR specification (v1.0) defines a JAXR provider as an implementation of the JAXR API. Generally, a JAXR provider can be a JAXR provider for UDDI, a JAXR provider for ebXML, or a pluggable provider that supports both UDDI and ebXML. The JAXR provider for UDDI is a provider for UDDI only.
UDDI versions
A JAXR provider for UDDI accesses a UDDI registry that uses the UDDI v2 SOAP APIs only. The UDDI registry for UDDI v3 in this version of WAS supports the UDDI v1, 2 and 3 SOAP APIs. Therefore we can use the JAXR provider for UDDI to access this registry. We can also use the JAXR provider to access the UDDI registry for UDDI v2 in WAS v5.x.
To work with the UDDI v3 SOAP APIs, use the UDDI v3 Client for Java; we cannot use JAXR.
Capability level
The JAXR specification defines two capability profiles, capability level 0 and capability level 1. The JAXR API documentation categorizes each JAXR method as either level 0 or level 1. Generally, a JAXR provider for UDDI has capability level 0 and supports all level 0 methods, whereas a JAXR provider for ebXML has capability level 1 and supports all level 0 and level 1 methods. The JAXR provider for UDDI is a capability level 0 provider, and supports only level 0 methods.
Authentication and security
The javax.xml.registry.authenticationMethod connection property determines which method the JAXR provider uses to authenticate with the UDDI registry.
The JAXR provider uses UDDI v2 SOAP Inquiry and Publish APIs. These APIs are protected, as described in the topic about access control for UDDI registry interfaces.
We can use SSL to encrypt HTTP traffic between the JAXR provider for UDDI and the UDDI registry.
Related concepts:
JAXR provider for UDDI internal taxonomies
JAXR provider logging and messages
Access control for UDDI registry interfaces
Related
Use the UDDI registry