What about the option of adding support for messageFormat in logger itself in a
future release?
(which release?)
Scott Deboy
-Original Message-
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Sun 9/2/2007 10:38 PM
To: Log4J Users List
Subject: Re: 1.3 {} notation available in 1.2.
Hi thanks i reverted to 1.2 with the extras however im now getting
these errors,
log4j:WARN Continuable parsing error 58 and column 76
log4j:WARN Element type "rollingPolicy" must be declared.
log4j:WARN Continuable parsing error 72 and column 16
log4j:WARN The content of element type "appender
On Sep 2, 2007, at 3:13 PM, dirk ooms wrote:
Hi,
i was using log4j 1.3, but i am moving back to 1.2.15 now. i often
used the
{} symbols in my log statements, e.g. logger.info("blahblah {}",
value);
1.2.x does not seem to understand this. is there any extension to
1.2.x that
supports
On Sep 2, 2007, at 11:00 PM, Daniel Rossi wrote:
Hi there, ive been developing upon log4j alpha 1.3 for quite a
while to use some new features. I believe it is now a dead branch.
What am i suppose to be using, I need the new
org.apache.log4j.rolling.RollingFileAppender package and the
ro
Hi there, ive been developing upon log4j alpha 1.3 for quite a while
to use some new features. I believe it is now a dead branch. What am
i suppose to be using, I need the new
org.apache.log4j.rolling.RollingFileAppender package and the rolling
policy for a project im working on which requi
Yes, in the extras library you'll find LogMF and LogSF. You make static calls
on LogMF or LogSF directly, passing in the logger.
I think we can integrate these methods into logger itself in an upcoming
release.
Link to extras:
http://logging.apache.org/log4j/companions/extras/index.html
Link
Hi Dirk,
Have you considered using the SLF4J API? It supports log4j 1.2 as well as other
logging systems. Moreover, you would not need to change your code since SLF4J
supports parameterized syntax you are currently using.
HTH,
dirk ooms wrote:
Hi,
i was using log4j 1.3, but i am moving bac
Hi,
i was using log4j 1.3, but i am moving back to 1.2.15 now. i often used the
{} symbols in my log statements, e.g. logger.info("blahblah {}", value);
1.2.x does not seem to understand this. is there any extension to 1.2.x that
supports this notation?
cheers,
dirk
-
