Why does the JAXR API not use UDDI terms and concepts?
A. The JAXR API is not specific to UDDI or any other registry specification. It is an abstraction API that covers multiple specifications. It is designed to enable developer choice in the use of a Web service registry and/or repository. The JAXR API uses UDDI terms and concepts when they fit the JAXR information model (for example, Service, ServiceBinding, and method names in BusinessQueryManager and BusinessLifeCycleManager).
Related Questions
- You are responsible for introducing terms such as mantra, astra and shaastra in the branding lexicon. How do these three concepts work?
- Youve mentioned the terms or concepts of Darwinian synthesis as providing a lingua franka. Do you see signs that that may be changing?
- Why is JAXR an abstraction API and not targeted to a specific registry such as UDDI or ebXML?
