Seems very ad-hoc to me. Why?
If you change the ILogger instance you can't assume that the change will propage to others instances for the same component. If we put that on the standard API, it will lead people to confusion: "what will be the behavior? depends on the LoggerManager implementation". The ILogger should be therefore immutable.
-- Cheers, hammett http://www.digitalcraftsmen.com.br/~hammett
----- Original Message ----- From: "Jorge CAMPOS" <[EMAIL PROTECTED]>
Hi!
I've modified the org.apache.avalon.framework.logger.Logger interface to add
a changeLevel method... I've also changed the implementations to support
this method... In this way the log level can be reset at runtime.
What do you think about the approach? I've speculated changing LoggerManager
instead, but since you can get a specific logger from the LoggerManager the
right place seemed to be Logger.
If it is OK, is it possible to post it somewhere for consideration towards its inclusion in the framework?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
