Or I can keep using log4j :-)
And patch it myself as needed -- as it is indeed hard to get necessary
improvements into log4j 1.2.x at this point. I have my own Java 5
specific changes to reduce locking, etc, at this point.
Ceki Gulcu wrote:
Jess Holle wrote:
To be fair and clear, my usage requires that my both custom appenders
and layouts receive the message Object I pass, not just a string.
*This* is critical. It is the difference between a logging system
being a simple string pipe and a /rich /log event data pump. The
trappings as to how exactly this occurs are less important as long as
this capability remains and is very efficient.
Jess,
You should have a look at logback which is designed around the
principle of specialized processing pipelines. There is logback-core,
which is logging agnostic, and there is logback-classic (equivalent of
log4j) and there is logback-access. The latter two are built on top of
logback-core and are mostly specialized processing chains for events
of type ILoggingEvent (logback-class) and of type AccessEvent
(logback-access). Of course, this does not preclude passing arbitrary
objects to logback-classic.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
