Return-Path: 
 <log4j-dev-return-5007-qmlist-jakarta-archive-log4j-dev=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-log4j-dev-archive@apache.org
Received: (qmail 87979 invoked from network); 18 Jul 2003 12:44:45 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 18 Jul 2003 12:44:45 -0000
Received: (qmail 22024 invoked by uid 97); 18 Jul 2003 12:47:15 -0000
Delivered-To: qmlist-jakarta-archive-log4j-dev@nagoya.betaversion.org
Received: (qmail 22016 invoked from network); 18 Jul 2003 12:47:15 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 18 Jul 2003 12:47:15 -0000
Received: (qmail 87647 invoked by uid 500); 18 Jul 2003 12:44:36 -0000
Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:log4j-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:log4j-dev-help@jakarta.apache.org>
List-Post: <mailto:log4j-dev@jakarta.apache.org>
List-Id: "Log4J Developers List" <log4j-dev.jakarta.apache.org>
Reply-To: "Log4J Developers List" <log4j-dev@jakarta.apache.org>
Delivered-To: mailing list log4j-dev@jakarta.apache.org
Received: (qmail 87598 invoked from network); 18 Jul 2003 12:44:36 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 18 Jul 2003 12:44:36 -0000
Received: (qmail 22008 invoked by uid 50); 18 Jul 2003 12:47:07 -0000
Date: 18 Jul 2003 12:47:07 -0000
Message-ID: <20030718124707.22007.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: log4j-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 21707] New:  -
    Problem with <categoryFactory> in log4j.xml for LoggerFactory sub-class
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21707>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21707

Problem with <categoryFactory> in log4j.xml for LoggerFactory sub-class

           Summary: Problem with <categoryFactory> in log4j.xml for
                    LoggerFactory sub-class
           Product: Log4j
           Version: 1.2beta
          Platform: All
               URL: na
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Configurator
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: apache-bugzilla@ueltschi.net
                CC: apache-bugzilla@ueltschi.net


Hi all,

We are using log4j 1.2.8. in our project (J2EE on WLS server). We have
sub-classed the Logger and LoggerFactory according to the examples. We are using
an XML file for configuration.

When we use <logger> or <category> (without the class attribute) and
<categoryFactory> in our log4j.xml, the DOMConfigurator is creating Logger
instances (instead of sub-classes created by our factory) during startup:

<log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>
  <appender name="STDOUT" class="org.apache.log4j.ConsoleAppender">
    <layout class="org.apache.log4j.PatternLayout">
      <param name="ConversionPattern" value="%-5p %d{dd.MM HH:mm:ss,SSS}
%-30.30c [%m]\t%x %n"/>
    </layout>
  </appender>
  <logger name="ch.postfinance.fw.FrontController">
    <level value="INFO"/>
  </logger>
  <category name="ch.postfinance.fipo.base.AdminServlet">
    <level value="INFO"/>
  </category>
  <category name="ch.postfinance.fipo.base.FipoFrontController"
class="ch.postfinance.log.PFLogger">
    <level value="INFO"/>
  </category>
[... more categories ...]
  <root>
    <priority value ="WARN" />
    <appender-ref ref="STDOUT" />
  </root>
  <categoryFactory class="ch.postfinance.log.PFLoggerFactory"/>
</log4j:configuration>

--------------------------- Debug output: -------------------------------
     [java] log4j: Threshold ="null".
OK   [java] log4j: Desired category factory: [ch.postfinance.log.PFLoggerFactory]

BAD  [java] log4j: Retreiving an instance of org.apache.log4j.Logger.
     [java] log4j: Setting [ch.postfinance.fw.FrontController] additivity to [true].
     [java] log4j: Level value for ch.postfinance.fw.FrontController is  [INFO].
     [java] log4j: ch.postfinance.fw.FrontController level set to INFO

BAD  [java] log4j: Retreiving an instance of org.apache.log4j.Logger.
     [java] log4j: Setting [ch.postfinance.fipo.base.AdminServlet] additivity to
[true].
     [java] log4j: Level value for ch.postfinance.fipo.base.AdminServlet is  [INFO].
     [java] log4j: ch.postfinance.fipo.base.AdminServlet level set to INFO

GOOD [java] log4j: Desired logger sub-class: [ch.postfinance.log.PFLogger]
     [java] log4j: Setting [ch.postfinance.fipo.base.FipoFrontController]
additivity to [true].
     [java] log4j: Level value for ch.postfinance.fipo.base.FipoFrontController
is  [INFO].
     [java] log4j: ch.postfinance.fipo.base.FipoFrontController level set to INFO
-------------------------------------------------------------------------

BUG: (?)

Why is not the LoggerFactory sub-class specified by <categoryFactory> used to
create <logger> or <category> instances, unless we use the "class" attribute for
the category tag?

TIA and cheers,

Tom Ueltschi

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org