Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Subject: Re: [logging] How to get logging to use new Monolog subclass
From: Simon Kitching <simon@ecnetwork.co.nz>
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
In-Reply-To: <001901c43667$e4395330$1700a8c0@talicnitom>
References: <005e01c43664$8c926390$1700a8c0@talicnitom>
	 <1084176662.5614.136.camel@pcsimon>
	 <001901c43667$e4395330$1700a8c0@talicnitom>
Content-Type: text/plain
Message-Id: <1084179375.5443.174.camel@pcsimon>
Mime-Version: 1.0
Date: Mon, 10 May 2004 20:56:16 +1200
Content-Transfer-Encoding: 7bit

On Mon, 2004-05-10 at 20:22, Igor Smirnov wrote:
> Hollowing Simon's suggestion, I am posting the same question under another
> Subject.
> 
> And to be more specific: I am working tiwht Monolog logger that implements
> and extends log4j functionality. I needed a new Log impl. in commons logging
> to be able to use Monolog logger with tomcat.
> Hopefully this clears it up. And here's the first post:
> 
> I've working with commons logging for the past week and have implemented a
> new logger within for my needs.
> Now, since I am not confortable with the whole commons package yet and the
> user's guide doesn't help much, could anyone explain me step by step how to
> set-up my system to use the new logger?

Cool, I'll have to look into monolog a bit.


As Jose mentioned, you can just set a system property on the jvm command
line:
  java -Dorg.apache.commons.logging.Log=your.log.class
(described in the LogFactoryImpl javadoc)

This is fine for debugging, but isn't very nice when building
frameworks, etc. But from a quick peek at the code, it looks like you
can also create a file "commons-logging.properties" and put it in the
classpath, with these contents:

org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
org.apache.commons.logging.Log=your.log.class

And as a third option, it looks like you could define your own
LogFactory subclass, and then specify it by creating a file:
  META-INF/services/org.apache.commons.logging.LogFactory
with its first line being:
  your.logfactory.class


I've only used the -D approach myself, so the above might be wrong. As
always, the source code is the official and final documentation! The
LogFactory and LogFactoryImpl classes are the ones that control all this
behaviour.

Regards,

Simon


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