Return-Path: 
 <log4j-dev-return-11152-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org>
Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org
Received: (qmail 71030 invoked from network); 19 Sep 2005 02:53:53 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 19 Sep 2005 02:53:53 -0000
Received: (qmail 57813 invoked by uid 500); 19 Sep 2005 02:53:52 -0000
Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org
Received: (qmail 57771 invoked by uid 500); 19 Sep 2005 02:53:52 -0000
Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-dev-unsubscribe@logging.apache.org>
List-Help: <mailto:log4j-dev-help@logging.apache.org>
List-Post: <mailto:log4j-dev@logging.apache.org>
List-Id: "Log4J Developers List" <log4j-dev.logging.apache.org>
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Delivered-To: mailing list log4j-dev@logging.apache.org
Received: (qmail 57757 invoked by uid 99); 19 Sep 2005 02:53:52 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Sep 2005 19:53:52 -0700
X-ASF-Spam-Status: No, hits=0.1 required=10.0
	tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: 204.127.198.54 is neither permitted nor
 denied by domain of hoju@visi.com)
Received: from [204.127.198.54] (HELO rwcrmhc12.comcast.net) (204.127.198.54)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Sep 2005 19:54:00 -0700
Received: from nicki.visi.com
 (c-66-41-141-26.hsd1.mn.comcast.net[66.41.141.26])
          by comcast.net (rwcrmhc14) with SMTP
          id <2005091902534701400oknare>; Mon, 19 Sep 2005 02:53:48 +0000
Message-Id: <5.2.1.1.0.20050918214511.035b8fe0@127.0.0.1>
X-Sender: hoju@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sun, 18 Sep 2005 21:53:44 -0500
To: "Log4J Developers List" <log4j-dev@logging.apache.org>
From: Jacob Kjome <hoju@visi.com>
Subject: Re: JoranConfigurator problems
In-Reply-To: <E45E5CC99D174847A32B0970834F177C0F64A1@csicorp6.pdxcsi.com
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Relayed-By: GPGrelay Version 0.959 (Win32)
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

At 11:28 PM 9/17/2005 -0700, you wrote:
 >I've noticed two issues with an xml-based configuration that works fine with
 >the 1.2.x jars but does not work using log4j 1.3x alpha jars:
 >
 >1. An appender that's defined but not referenced is still constructed and
 >activateOptions is called (the IRC appender in the example below)
 >
 >2. Using a 'category' instead of 'logger' node prevents the configuration
 >from being loaded with the following error (using a 'logger' node works 
fine):
 >Reported error: "no applicable action for <category>, current pattern is
 >[/configuration/category]" at line 27 column 24
 >Reported error: "no applicable action for <priority>, current pattern is
 >[/configuration/category/priority]" at line 28 column 32
 >Reported error: "no applicable action for <appender-ref>, current pattern is
 >[/configuration/category/appender-ref]" at line 29 column 30
 >

Isn't this an opportunity to get rid of <category> and <priority> once and 
for all?  In many cases, Logj4-1.2.xx XML config files have to be slightly 
rewritten to work with the JoranConfigurator anyway.  We've been saying not 
to use these tags for a few years now.  Time to dump them, not perpetuate them.

Jake


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