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: Configuration
Date Mon, 03 Jul 2006 14:22:25 GMT
A document has been updated:

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

Document ID: 1162
Branch: main
Language: default
Name: Configuration (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 7/3/06 2:22:11 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: 6964 bytes (previous version: 5082 bytes)
Content diff:
(76 equal lines skipped)
    lookup the Settings bean. This bean provides access to all available properties.
    </p>
    
+++ <h1>Logging</h1>
+++ 
+++ <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>
+++ 
+++ <h2>Location of the logging configuration</h2>
+++ 
+++ <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>
+++ 
+++ <h2>Overriding the log level</h2>
+++ 
+++ <p>For development you can override the configured log level from 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>
+++ 
+++ <h2>Shielded Classloading</h2>
+++ 
+++ <p>By default, Cocoon is configured to use shielded classloading. Therefore an
+++ own instance of Log4J is instantiated for just the Cocoon web application. If
+++ you want to share a global Log4J configuration between web applications, you
+++ have to turn off the shielded classloading for the whole Cocoon instance of for
+++ just Log4J.</p>
+++ 
+++ <h2>Using your own logging system</h2>
+++ 
+++ <p>If you want to use your own logging system instead of Log4J you can setup a
+++ Logger bean in the root application context of Spring. This bean must be
+++ registered with the name <em>org.apache.avalon.framework.logger.Logger</em>
and
+++ it must conform to the interface with this name.</p>
+++ 
    <h1>Component Configurations</h1>
    
    <p>While older versions of Cocoon used one single big file for the configuration
(21 equal lines skipped)
    Avalon based configuration files from "config/xconf" and all Spring bean
    configuration files from "config/spring" are included.</p>
    
+++ <h1>Shielded Classloading</h1>
+++ 
+++ <p>TBD</p>
+++ 
    </body>
    </html>


Fields
======
no changes

Links
=====
no changes

Custom Fields
=============
no changes

Collections
===========
no changes

Mime
View raw message