Hi Robert,
You really should take a look at the coded I posted. Especially the
wrappers package!!!
You can get what is the log level of LogKit by testing the
m_logger.isDebugEnabled();
m_logger.isInfoEnabled();
m_logger.isXXXXEnabled();
...methods in the right order.
This gives you only 5 log levels, but that is the design defended by
both the Log4J and LogKit guys. And since you want the lest common
denominator, maybe that is the way to go.
Again, you should take a look at the code I posted. This is 1 line
on that code:
* @author <a href="mailto:[EMAIL PROTECTED]";>Peter Donald</a>
Peter knows ALL the 3 logging APIs VERY WELL. He was one of the
authors of LogKit and he also seems to know Log4J inside out.
As I told you, I picked this stuff from Avalon, I use it for 3
months for my logging and IT WORKS!
I am logging > 75000 lines of code with this!
Please take a look.
Have fun,
Paulo Gaspar
> -----Original Message-----
> From: robert burrell donkin [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 7:49 PM
> To: Jakarta Commons Developers List
> Subject: Re: how should log levels work? [Was Re: [Logging] default log
> level]
>
>
>
> On Wednesday, January 9, 2002, at 11:19 PM, Scott Sanders wrote:
>
> > From what you are saying then I would like to propose Paulo's suggestion
> > of removing setLevel(). The slippery slope is much too steep :(
>
> now i'm thinking about it, this route has difficulties as well. some
> loggers (eg. LogKit) think that being able to get the current
> priority for
> the logger is too much of a security risk. so you can't rely on the
> wrapper being able to get a decent value for getLogLevel.
> components would
> therefore have to avoid using this the getter since the effect would be
> log system dependent. so i guess that if you're removing the setter there'
> s an argument for removing getter as well.
>
> - robert
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
