3.4. Log4J
Prev | Chapter 3. Logging | Next

## 3.4. Log4J

When `kodo.Log` is set to `log4j`, Kodo will delegate to Log4J for logging. In a standalone application, Log4J logging levels are controlled by a resource named `log4j.properties`, which should be available as a top-level resource (either at the top level of a jar file, or in the root of one of the `CLASSPATH` directories). When deploying to a web or EJB application server, Log4J configuration is often performed in a `log4j.xml` file instead of a properties file. For further details on configuring Log4J, please see the Log4J Manual. We present an example `log4j.properties` file below.

Example 3.4. Standard Log4J Logging

    log4j.rootCategory=WARN, console
    log4j.category.kodo.Tool=INFO
    log4j.category.kodo.Runtime=INFO
    log4j.category.kodo.Remote=WARN
    log4j.category.kodo.DataCache=WARN
    log4j.category.kodo.MetaData=WARN
    log4j.category.kodo.Enhance=WARN
    log4j.category.kodo.Query=WARN
    log4j.category.kodo.jdbc.SQL=WARN
    log4j.category.kodo.jdbc.JDBC=WARN
    log4j.category.kodo.jdbc.Schema=WARN

    log4j.appender.console=org.apache.log4j.ConsoleAppender

Prev | Up | Next
3.3. Disabling Logging | Home | 3.5. Apache Commons Logging