Craig's point was that configuring commons-logging and configuring the
underlying logging implementation are two distinct things. Common-logging
will use its .properties file, just like always; and log4j will use the XML
configuration file required by the AsyncAppender.
HTHs,
Jamie
[EMAIL PROTECTED] on 09/17/2003 04:40:37 PM
Please respond to "Jakarta Commons Users List"
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Commons-loggin and AsyncAppender
That's exactly my point...the use of AsyncAppender requires an XML
formatted configuration file, not a java properties formatted configuration
file, and the commons-logging doesn't seem to work with such configuration
files.
Should I be posting this on the log4j mailing list?
On Wed, 17 Sep 2003 [EMAIL PROTECTED] wrote:
> Date: Wed, 17 Sep 2003 12:03:28 -0400
> From: [EMAIL PROTECTED]
> Reply-To: Jakarta Commons Users List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Commons-loggin and AsyncAppender
>
> I wish to use a log4j AsyncAppender behind the commons-logging facade.
The
> issue is that I know the use of AsyncAppenders requires an XML
> configuration file, and the DOMConfigurator to digest this config file.
Is
> this possible when using commons-logging?
>
Sure. Commons-logging doesn't care how you configure the underlying
logging system (Log4J in your case). Just follow the standard Log4J
documentation on how to set this up.
> Thanks.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
