At 02:53 PM 6/17/2003 -0400, Berin Loritsch wrote:
Ceki Gülcü wrote:
Of course, nothing prevents us from adding a getChildLogger(String
name) to the Logger class. Would that be sufficient for your needs?
For the short term, sure. Right now, the Avalon wrapper for Log4J
uses the following code snippet:
Logger getChildLogger(String subCat)
{
return new Log4JLogger(
Logger.getLogger(m_logger.getName() + "." + subCat));
}
It's not pretty, but it works.
It should not be too difficult (read trivial) to add these 4 lines of
code or equivalent thereof to the Logger class.
Not yet. I haven't looked at what is available and what is not.
For the quick rundown of Avalon LogKit log targets, we have:
File
Memory
JDBC
JMS
JavaMail
Servlet
Socket
As well as some file rotation strategies.
If Log4J already has all these then the last bullet point can be
ignored.
We don't have Memory, I mean a MemoryAppender. What is the use case
for a MemoryAppender?
Actually, the SMTPAppender is based on a cyclic buffer that sends off
an email when a triggering event occurs. Still that is quite different
than LogKit's MemoryTarget.
--
Ceki For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
In the USA the log4j manual is carried by Softpro books.
http://store.yahoo.com/softpro/2-9700369-0-8.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
