RE: methods to always log, regardless of the current priority

2004-01-28 Thread Tom Drake
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

RE: MDC copies

2004-01-28 Thread Christian . Hall
I don't think you can do a default deep copy unless you overload clone yourself. I agree with the point about performance. I suppose it depends on how much stuff is in MDC. Our use of AsyncAppender here is to push some longer-running stuff out of the primary thread, so unless the deep copy is par

RE: methods to always log, regardless of the current priority

2004-01-28 Thread Shapira, Yoav
Howdy, Or you could let the logging configuration lie with the system administrator or application deployer, where it should, and specify your desired behavior in your documentation. Yoav Shapira Millennium ChemInformatics >-Original Message- >From: Elias Ross [mailto:[EMAIL PROTECTED]

Re: MDC copies

2004-01-28 Thread Ceki Gülcü
Christian, We could simply add a deep MDC copy method to LoggingEvent and add an option to AsyncAppender so that deep MDC copy method would be called. The problem with deep copying, or even with the shallow copying we do currently, is the incurred performance hit. The whole point of AsyncAppen

Re: Thoughs on Level.java

2004-01-28 Thread Ceki Gülcü
At 11:45 PM 1/27/2004 -0800, Elias Ross wrote: On Tue, 2004-01-27 at 22:58, Elias Ross wrote: > Level ALWAYS = new Level(ALWAYS_INT, "INFO", 7); Okay, looking at the JavaDoc, Level doesn't have a public constructor. Why not? At first glace it didn't make a whole lot of sense. Level does not ha

Thoughs on Level.java

2004-01-28 Thread Elias Ross
On Tue, 2004-01-27 at 22:58, Elias Ross wrote: > Level ALWAYS = new Level(ALWAYS_INT, "INFO", 7); Okay, looking at the JavaDoc, Level doesn't have a public constructor. Why not? At first glace it didn't make a whole lot of sense. I then realized it must have been done this way to allow config

Re: methods to always log, regardless of the current priority

2004-01-28 Thread Elias Ross
On Tue, 2004-01-27 at 18:43, Sheward, Barry wrote: > Hi, > > We use Log4J extensively and find that sometimes we always want to log a message, > but the message is simply for informational purposes. Using > Logger/Category.fatal() would potentially frighten users, You could use a custom Level