cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: Logging
Date Thu, 04 Jan 2007 15:12:06 GMT
A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1257.html

Document ID: 1257
Branch: main
Language: default
Name: Logging (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 1/4/07 2:52:46 PM
Updated by: Carsten Ziegeler

A new version has been created, state: publish

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 1943 bytes (previous version: 1989 bytes)
Content diff:
    <html>
    <body>
    
--- <p>Cocoon uses <a href="http://logging.apache.org/log4j">Log4J</a> by
default
--- and all log statements are written to a single log file in the temporary
--- directory of the application server. The configuration for log4j is in the
--- WEB-INF directory in the log4j.xconf file. The logging can be controlled in
--- various ways as described below.</p>
+++ <p>Cocoon uses <a href="http://jakarta.apache.org/commons/logging/">Commons
+++ Logging</a> by default and provides support for using Log4j (through commons
+++ logging). The usual Cocoon web application sets up Log4j through the
+++ <a href="daisy:1303">Cocoon Spring Configurator</a>.</p>
    
--- <h1>Location of the logging configuration</h1>
+++ <p>The default configuration for Log4j is in the global application context
+++ definition. Cocoon loads <em>WEB-INF/cocoon/log4j.xconf</em> as the
+++ configuration for Log4J. If you want to make any changes to the configuration
+++ file, it is advisable to not alter this default file but instead use your own
+++ configuration. Just change the reference in the application definition. This
+++ sample configuration file sets up Log4j to log all statements to a single log
+++ file in the temporary directory of the application server. The logging can be
+++ controlled in various ways as described below.</p>
    
--- <p>By default, Cocoon loads <em>WEB-INF/log4j.xconf</em> as the configuration
--- for Log4J. If you want to make any changes to the configuration file, it is
--- advisable to not alter this default file but instead use your own configuration.
--- By setting the <em>org.apache.cocoon.logging.configuration</em> property in
your
--- properties, you can point to a different configuration file.</p>
--- 
--- <h1>Bootstrap log level</h1>
--- 
--- <p>TBD</p>
--- 
--- <h1>Environment Logging Category</h1>
--- 
--- <p>TBD</p>
--- 
--- <h1>Cocoon Logging Category</h1>
--- 
--- <p>TBD</p>
--- 
    <h1>Overriding the log level</h1>
    
--- <p>For development you can override the configured log level from your Log4J
+++ <p>For development you can override the configured log level for your Log4J
    configuration by setting the property
--- <em>org.apache.cocoon.override.loglevel</em> with the name of the level. This
is
--- for example very usefull to set the log level to debug for development purposes
--- without changing the logging configuration.</p>
+++ <em>org.apache.cocoon.override.loglevel</em> to the name of the level. For
+++ example this is very usefull to set the log level to debug for development
+++ purposes without changing the logging configuration.</p>
    
    <h1>Shielded Classloading</h1>
    
(15 equal lines skipped)


Mime
View raw message