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 Deprecated feature: From WebSphere® Application Server Version 8.0, Java API for XML Registries (JAX-R) APIs are deprecated. The Java Platform, Enterprise Edition (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 your applications use JAX-R, then you might consider using UDDI 3.depfeat
UDDI4J Logging
The JAXR provider for UDDI uses UDDI4J Version 2 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.

Concept topic    

Terms and conditions for information centers | Feedback

Last updated: April 18, 2014 05:01 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=cwsu_jaxr_log
File name: cwsu_jaxr_log.html