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 logging and messages

The Java API for XML Registries (JAXR) provider for UDDI uses UDDI4J logging, commons logging, and some standard messages.

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

UDDI4J Logging

The JAXR provider for UDDI uses UDDI4J v2 to communicate with the UDDI registry. UDDI4J has its own logging.

To switch on UDDI4J logging, set the org.uddi4j.logEnabled system property to true. The XML request and response bodies of every UDDI request are sent to the standard error log.

Trace

Entry, exit, exception, warning, and debug trace is provided by Commons Logging (JCL). Trace is created only if the JAXR client configures it. Entry, exit, and debug trace uses the debug level of logging. Exception and warning trace uses the information level of logging. Additionally, information-level logging is provided before each UDDI4J request is made.

Standard error log messages

The InternalTaxonomyManager, EnumerationManager, and PostalSchemeManager objects send warning messages to the System.err log if there is an error condition that does not justify an exception, but does require an information message. For example, warning messages are sent if a file contains a line that is not valid, or if a tModel entity that corresponds to an internal taxonomy cannot be found in the registry.

Use the JAXR provider for UDDI
Commons Logging

+

Search Tips   |   Advanced Search