I see. As of now I've changed the implementations of Logger within framework (I saw some more in the containerkit module, I will change those too).
Now I need to propagate the new level to the childLoggers. And if we stick to the Logger approach, this responsibility will belong to Logger. Another posibility could be changing the AbstractLogEnabled and LogEnabled to add a changeLogLevel method. What do you think? Cheers Jorge -----Original Message----- From: hammett [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 05, 2005 12:22 AM To: Excalibur Developers List Subject: Re: Avalon-Excalibur Logger 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
