On 11/16/2011 10:27 AM, Steve Cohen wrote:
On 11/16/2011 12:53 AM, Ceki Gulcu wrote:
Hi Steve,
Logback components, including appenders, should use the status manager. If you look at logback code you should see invocations of addInfo, addWarn or addError methods strewn throughout the code.
-- Ceki
On 12.11.2011 23:14, Steve Cohen wrote:
We have a custom appender that may itself need to issue logging statements. But placing a logger in such a class causes various exceptions on initialization and loading. So we are resorting to System.out.println for lack of a better solution.
I suppose there must be a better way. What would that be?
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
Thanks, Ceki. I am looking into this. I have a question, though. If you, for example, call addInfo() from an appender, which Logger decides whether or not to log it? The root logger? _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
Looking at this a little more deeply, I see that this works, in the case of the OnConsoleStatusListener, via simply writing on the console. But it seems that the level you choose to add (addInfo() vs addWarn() for example) affects only the status reported on the output device and there is no filtering available based on these "levels". Is this correct?