Yes, there's a reason (if I got it right): All log configuration is done in a config file or by the container (means: it is done from outside). And I think logging and logging configuration (ex. Priority) are two different concerns, so they shouldn't be in the same interface.
So, you should not set the logging priority within your code. Having the priorities in a config file enables you to switch on logging for a particular category at the customer site if something goes wrong. You can't do that if you're hardcoding the priority. > The org.apache.avalon.framework.logger.Logger > interface is a wrapper for the various loggers that > are available (ie. logkit, log4j, jdk14). However > it is missing a setPriority method which I need. > > Logkit/log4J/jdk14 all provide this method in their > Logger interface. Any reason it is not there in the > Framework Logger? > If not, I will provide patches to support it. Cheers, Jeremias M�rki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Fon +41 41 317 20 20 - Fax +41 41 317 20 29 Internet http://www.outline.ch -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
