Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of mfncooper@gmail.com
 designates 64.233.184.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=RymE3OnRnIdTVkooaPA+aej+pfcMMa8Jw2WsCjUrsFeZDIyH1yFDBGtcPB8Ap6vISt+2ZhXFAHP4CQ/7NMUd5dYhO5g9z9qXcX55zpJcqSdpUS1ozfKdY7MEvWZ91Gu70np+mql3I9dMwhTmE5VfQalvmS5t8plk+5LL1OU92KU=
Message-ID: <16d6c620041227085663ce0d3f@mail.gmail.com>
Date: Mon, 27 Dec 2004 08:56:00 -0800
From: Martin Cooper <mfncooper@gmail.com>
Reply-To: Martin Cooper <mfncooper@gmail.com>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: commons-logging auto-detection WAS: [logging] Enterprise Common
 Logging... dare we say 2.0?
In-Reply-To: <6.0.3.0.0.20041227124408.03bc2c70@mail.qos.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
References: <6.0.3.0.0.20041226171859.03e7c4f0@mail.qos.ch>
	 <20041227021515.399A91EC073@mail.qos.ch>
	 <6.0.3.0.0.20041227124408.03bc2c70@mail.qos.ch>

On Mon, 27 Dec 2004 12:49:45 +0100, Ceki G=FClc=FC <ceki@qos.ch> wrote:
> At 03:05 AM 12/27/2004, Charles Daniels wrote:
>=20
> >If I understand the JCL discovery mechanism correctly, it actually
> >should work just fine in the scenario you describe above.  For it to
> >work, you would not set the org.apache.commons.logging.LogFactory system
> >property, because, as you pointed out, system properties are JVM-wide.
> >Rather, for individual applications to use distinct underlying logging
> >implementations, you can simply place a commons-logging.properties file
> >in each application context (in WEB-INF/classes), setting the
> >org.apache.commons.logging.LogFactory property as appropriate in each
> >distinct commons-logging.properties file.  Since these properties files
> >will be loaded via distinct context class loaders, each application can
> >use distinct logging implementations.
>=20
> Good point. This will require some understanding by the user about the
> classloader delegation mechanism used by the app server, which varies
> from vendor to vendor or even from version to version of an app server
> by the same vendor.  Nevertheless, I stand corrected.

Given that making web applications self-contained, such that
everything required by the app is incorporated in the war file, is a
standard "best practice", I don't think there will be that much of a
need to educate people further with respect to class loader mechanisms
in order to understand how to use logging properly.

--
Martin Cooper


>=20
> --
> Ceki G=FClc=FC
>=20
>   The complete log4j manual: http://qos.ch/log4j/
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>=20
>

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