> Manipulating the repository threshold might accomplish what > you are trying to do. Every event is evaluated relative to > the repository threshold before being evaluated against > logger and appender thresholds. If you set the repository > threshold to "info" but set the loggers and appenders to > "debug", only "info" and higher messages will be processed > until the threshold is lowered to "debug".
When I understood the threshold correctly, this would OTOH for debugging of a single class (=logger) require to lower the threshold to "debug" and reconfigure all other loggers to "not debug". So: this setup would make it impossible to set some loggers to "error" or "fatal" by default, as every logger *has* to be configured for "debug" to make the scenario work. Any other configuration on user (app.-dev.) site would destroy this functionality. Am I right? > > The repository threshold can be specified in a configuration file: > > <log4j:configuration threshold="info"...> > > or > > log4j.threshold=info > > or by code: > > logger.getLoggerRepository().setThreshold(Level.DEBUG); > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > *********************************************************************** Die Information in dieser email ist vertraulich und ist ausschliesslich fuer den/die benannten Adressaten bestimmt. Ein Zugriff auf diese email durch andere Personen als den/die benannten Adressaten ist nicht gestattet. Sollten Sie nicht der benannte Adressat sein, loeschen Sie bitte diese email. *********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
