simpler would be to serialize the configuration object tree. But
this would not be human readable. That may be okay, however, since it could
be 'visualized' via the JMX console.
Regards,
Tom Drake
-Original Message-
From: Rob Butler [mailto:[EMAIL PROTECTED]
Sent: Thursday,
The simplest thing to do is to set aside a logger name/hierarchy for this
purpose:
Ex)
If your logger names correspond to your classnames (a common approach) then
you are using names like com.foobar.p1.c1
Then your loggers for this hierarchy could do the normal level based
filtering.
When you ne
Couldn't this problem be solved by making this (serialization) behavior
configurable. Moving the serialization logic out of LoggingEvent and into a
strategy class. The default behavior could be identical to existing code.
Alternate strategy impls could be written to do other interesting things,
lik
Title: Message
I
would ask you why you want to extend the Logger class. Log4J provides a number
of ways of modifying default behaviors. You may find that you can meet your
needs without extending logger.
-Original Message-From: Paul Glezen
[mailto:[EMAIL PROTECTED] Sent: Tues
