Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - UDDI registry > Develop with the UDDI registry > Use the JAXR provider for UDDI
JAXR provider for UDDI internal taxonomies
The Java API for XML Registries (JAXR) provider for UDDI supplies a number of internal taxonomies.
Deprecated feature: In WAS 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.
depfeat
The following table shows the internal taxonomies that the JAXR provider for UDDI supplies.
| Taxonomy | ClassificationScheme name (UDDI tModel name) | ClassificationScheme id (UDDI v2 tModelKey) |
|---|---|---|
| NAICS 1997 | ntis-gov:naics:1997 | UUID:C0B9FE13-179F-413D-8A5B-5004DB8E5BB2 |
| NAICS 2002 | ntis-gov:naics:2002 | UUID:C0B9FE13-179F-413D-8A5B-5004DB8E5BB2 |
| UNSPSC 3.1 | unspsc-org:unspsc:3-1 | UUID:DB77450D-9FA8-45D4-A7BC-04411D14E384 |
| UNSPSC 7 | unspsc-org:unspsc | UUID:CD153257-086A-4237-B336-6BDCBDCC6634 |
| ISO3166 2003 | ubr-uddi-org:iso-ch:3166-2003 | UUID:4E49A8D6-D5A2-4FC2-93A0-0411D8D19E88 |
The tModel entities that correspond to all these taxonomies are available in the UDDI v3 registry. If you use the JAXR provider to access a UDDI v2 registry, only the tModel entities that correspond to the NAICS 1997, UNSPSC 3.1, and ISO3166 taxonomies are available.
Each internal taxonomy is loaded into memory once for each JAXR Connection. The classification scheme of the taxonomy is created when the connection is created. At this time, the associated UDDI tModel entity is obtained from the registry and used to populate the ClassificationScheme attributes. The concept object tree of the taxonomy is not created until the first time the user requests the ClassificationScheme object. All subsequent requests for the same internal taxonomy that use the same connection return the same object tree.
Do not modify any part of the concept object tree programmatically. There is only one classification scheme and concept object tree for each internal taxonomy for each connection, and if you modify the concept tree programmatically, all future requests for this taxonomy that use the same connection return the modified objects, which might not be valid. If you modify the concept tree programmatically, the associated taxonomy data file does not change.
To change the values in a user-defined internal taxonomy, change the taxonomy data file, then create a new connection to pick up the changes in a new concept tree.
Similarly, do not modify an internal classification scheme programmatically, except to modify and then save a user-defined internal classification scheme. A new connection is not required to pick up programmatic changes.
Create a custom internal taxonomy for the JAXR provider
Use the JAXR provider for UDDI