Re: Thoughs on Level.java

2004-01-30 Thread Ceki Gülcü
Barry, I think that the "always" printing functionality could be of general use. There are several ways of approaching this. 1) Extending Logger (category) As you have done. Casual users are strongly discouraged from extending the Logger class. A casual user is defined as any developer who is

Re: Thoughs on Level.java

2004-01-30 Thread Barry Sheward
Ceki, Here is a copy of my previous email... Hi, We use Log4J extensively and find that sometimes we alwayswant to log a message, but the message is simply for informationalpurposes. Using Logger/Category.fatal() would potentially frightenu

Re: Thoughs on Level.java

2004-01-30 Thread Ceki Gülcü
At 02:00 PM 1/30/2004 -0500, Barry Sheward wrote: So Ceki, how would you go about trying to do what I want to do? The alternative to adding four methods to Category is having to subclass Level to include a new Level and use Category.log( Level, ... ) or subclass Category too. Either approach will

Re: Thoughs on Level.java

2004-01-30 Thread Barry Sheward
So Ceki, how would you go about trying to do what I want to do? The alternative to adding four methods to Category is having to subclass Level to include a new Level and use Category.log( Level, ... ) or subclass Category too. Either approach will eventually end up with us writing wrappers around

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