lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Biestro (JIRA)" <>
Subject [jira] Updated: (SOLR-549) Enable configurable logging (jul or log4j)
Date Wed, 23 Apr 2008 16:05:21 GMT


Henri Biestro updated SOLR-549:

    Attachment: solr-log4j.patch

This patch allows to re-route jul logging to log4j if desired; this does not try to change
the logging API - ie, the jul logging remains the choice- but gives the web application a
chance to initialize logging a bit differently and become log4j firendly.

It introduces a 'org.apache.solr.logging' package from which jul loggers are obtained; instead
of writing 'Logger log = java.util.logging.Logger.getLogger("blah");' you write 'Logger log
= org.apache.solr.logging.Logger("blah");'. The default behavior is maintained and so are
the dependencies.

The implementation classes that depend on log4j (1.2.15) are 'optionally' compiled so far
by changing the build.xml 'compile-common' target dependency from 'compile-logging' to 'compile-logging-log4j'.
More precisely if the 'org.apache.solr.logging.Configuration' class can be loaded , the framework
will return anonymous j.u.l.Loggers having one handler that convert their LogRecords into
log4j events, the log4j logger having the name of the intended j.u.l.Logger.
The code comments go through more details.

> Enable configurable logging (jul or log4j)
> ------------------------------------------
>                 Key: SOLR-549
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.3
>            Reporter: Henri Biestro
>         Attachments: solr-log4j.patch
> java.util.logging does not allow to easily create a self-sufficient 'war' with respect
to logging configuration.
> The java.util.logging.LogManager used by the application is always created by the container
and is thus only configurable through the container; furthermore, if one already uses say
log4j in a webapp that embeds Solr, it does not even seem possible to re-route jul logging
into log4j just by configuration.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message