to duplicate these features when log4j already fulfills
those requirements?
http://logging.apache.org/log4j/2.x/
HTH
Martin
Subject: Re: Origin of struts log messages misleading
To: user@struts.apache.org
From: nhar...@gmx.at
Date: Tue, 21 Jul 2015 13:00:02 +0200
Alright. Only need to be patient
log4j.appender.CACHE.ImmediateFlush=true //never implement cache without flush
if you dont RollingFileAppender will cache the original entry until its flushed
Martin
Subject: Re: Origin of struts log messages misleading
To: user@struts.apache.org
From: nhar...@gmx.at
Date: Wed, 22 Jul 2015
Alright. Only need to be patient then :-)
Thanks.
On 18.07.2015 19:55, Lukasz Lenart wrote:
2015-07-17 23:57 GMT+02:00 Norbert Harrer nhar...@gmx.at:
Hi.
I noticed, that all log messages from struts look like this:
Jul 17, 2015 11:31:39 PM com.opensymphony.xwork2.util.logging.jdk.JdkLogger
the same thread
why should anyone want to duplicate these features when log4j already fulfills
those requirements?
http://logging.apache.org/log4j/2.x/
HTH
Martin
Subject: Re: Origin of struts log messages misleading
To: user@struts.apache.org
From: nhar...@gmx.at
Date: Tue, 21 Jul 2015 13:00
Thanks, Martin, for your reply.
But aren't you talking about my own logging messages? I was talking
about the log messages from struts itself.
Kindest Regards,
Norbert.
On 18.07.2015 02:16, Martin Gainty wrote:
Norbert:
you can always dig out the class name e.g.
logger.getClass().getName()
2015-07-17 23:57 GMT+02:00 Norbert Harrer nhar...@gmx.at:
Hi.
I noticed, that all log messages from struts look like this:
Jul 17, 2015 11:31:39 PM com.opensymphony.xwork2.util.logging.jdk.JdkLogger
info
INFO: Parsing configuration file [struts-plugin.xml]
Jul 17, 2015 11:31:39 PM
Norbert:
you can always dig out the class name e.g.
logger.getClass().getName()
OR implement log4j and configure log4j.xml thusly:
Configuration status=warn name=MyApp packages=
Appenders
File name=MyFile fileName=logs/app.log
PatternLayout
Pattern%2 %d %p %c{1.} [%t]
7 matches
Mail list logo
