I am writing logs to log4j with Commons Logging in many projects and the only difficults I've found were with AppServer precedence of libraries.
You should try to configure log4j implementation first, and when this implementation works give a try with Monolog
Simon Kitching wrote:
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------------------------------------------------- Este correo electr�nico y, en su caso, cualquier fichero anexo al mismo, contiene informaci�n de car�cter confidencial exclusivamente dirigida a su destinatario o destinatarios. Queda prohibida su divulgaci�n, copia o distribuci�n a terceros sin la previa autorizaci�n escrita de Indra. En el caso de haber recibido este correo electr�nico por error, se ruega notificar inmediatamente esta circunstancia mediante reenv�o a la direcci�n electr�nica del remitente.
The information in this e-mail and in any attachments is confidential and solely for the attention and use of the named addressee(s). You are hereby notified that any dissemination, distribution or copy of this communication is prohibited without the prior written consent of Indra. If you have received this communication in error, please, notify the sender by reply e-mail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
