Maybe I don't understand your question, but wouldn't this do what you
want:
log.info(Context information... data: + renderableObject);
???
Cheers,
Hein
On Fri, 2002-08-02 at 14:39, Barry Kaplan wrote:
We've just started to use renderers, as it makes things a bit cleaner.
However, we
in the PatternLayout.
But it will affect performance if displayed with every logging message (as
will your code below, I believe).
-Mark
-Original Message-
From: Hein Meling [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 30, 2002 12:48 PM
To: Log4J Users List
Subject
hi.
sorry if this is not the right place for this kind of request, but i
don't want to subscribe to the developers list.
anyway, sometimes it may be very useful to log a stack trace, even if
there was no exception, in order to determine from where a method is
being called. is this idea
Jacob Kjome wrote:
It is very likely that the duplicates are entirely my fault, but I can't
see how. Can someone point it out to me?
Try setting the additivity flag to false; like this:
logger name=jgroup
level value=info/
appender-ref ref=STDOUT-INFO/
/logger
logger
Ciao,
If you use the ant build tool, you can specify the -D options quite
easily in the build.xml file, and you wouldn't have to retype it for
every run. See below for an example of passing -D options to an
application that can be started through an ant target, 'execdaemon'.
Otherwise,
Dear log4j users and experts,
Here is what I want to do: Log everything to file (level debug); and
log partially (level info) to the console, with some exceptions
specified with finer granularity that should have level debug.
My initial configuration file (see below) does not work; clearly
