 | This article includes alist of references,related reading, orexternal links,but its sources remain unclear because it lacksinline citations. Please helpimprove this article byintroducing more precise citations.(June 2013) (Learn how and when to remove this message) |
 | This articlerelies excessively onreferences toprimary sources. Please improve this article by addingsecondary or tertiary sources. Find sources: "Jakarta XML Registries" – news ·newspapers ·books ·scholar ·JSTOR(June 2013) (Learn how and when to remove this message) |
Jakarta XML Registries (JAXR; formerly Java API for XML Registries) defines astandardAPI forJakarta EEapplications to access and programmatically interact with various kinds ofmetadata registries. JAXR is one of theJava XML programming APIs. The JAXR API was developed under theJava Community Process as JSR 93.
JAXR provides a uniform and standard Java API for accessing different kinds of XML-based metadata registry. Current implementations of JAXR supportebXML Registry version 2.0, andUDDI version 2.0. More such registries could be defined in the future. JAXR provides an API for the clients to interact with XML registries and aservice provider interface (SPI) for the registry providers so they can plug in their registry implementations. The JAXR API insulates application code from the underlying registry mechanism. When writing a JAXR based client to browse or populate a registry, the code does not have to change if the registry changes, for instance from UDDI to ebXML.
Jakarta XML Registries (JAXR) was removed from Jakarta EE 9.[1]
