Jakarta Commons Logging provides a simple logging interface and thin wrappers for several logging systems. WebSphere Application Server supports Jakarta Commons Logging by providing a logger. The support does not change interfaces defined by Jakarta Commons Logging. The WebSphere Application Server logger is a thin wrapper for the WebSphere Application Server logging facility. The logger name is com.ibm.websphere.commons.logging.WsJDK14Logger. The logger can handle logging objects defined by either of the following:
A logging object is an object that holds logging entry information.
To better understand Jakarta Commons Logging, read Jakarta Commons and the specifications for Java Logging and for Common Base Event. To better understand use of the WebSphere Application Server logger, read Jakarta Commons Logging.
WebSphere Application Server provides the Jakarta Commons Logging binary distribution in its libraries directory. By default, the product uses the Jakarta Commons Logging LogFactory implementation and JDK14Logger.
Best practice: The default
configuration of Jakarta Commons Logging is stored in the commons-logging.properties file.
To specify the factory class to use with Jakarta Commons Logging in an application,
provide a file named org.apache.commons.logging.LogFactory,
located in META-INF/services directory, that contains
the name of the factory class on the first line. This is the configuration
mechanism for the JAR file service provider, as defined in JDK 1.3 and above.bprac
For an application to use the WebSphere Application Server logger, the application must provide its own configuration for the logger. To configure an application to use the WebSphere Application Server logger, complete the steps that follow.