Steve, Those messages aren't sent though the appenders--instead it goes through StatusListeners.
http://logback.qos.ch/manual/joran.html#statusListener -- TJ On Wed, Nov 16, 2011 at 10:27 AM, Steve Cohen <[email protected]>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 >> [email protected] >> http://mailman.qos.ch/mailman/**listinfo/logback-user<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 > [email protected] > http://mailman.qos.ch/mailman/**listinfo/logback-user<http://mailman.qos.ch/mailman/listinfo/logback-user> >
_______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
