For me, the concept of an appender is to "rewrite" the logging event in a different kind and not to be used as listening system. With using, a NullAppender you use concept in place of another. But perhaps, it was a bad idea.
-----Message d'origine----- De�: Jim Moore [mailto:[EMAIL PROTECTED] Envoy�: lundi 11 octobre 2004 18:57 ��: Log4J Developers List Objet�: Re: Logging Event Listener I'm unclear of how a "listening" system would be different than the NullAppender solution you proposed. Can you give an example? On Mon, 11 Oct 2004 16:58:18 +0200, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I was wondering, if it would be great to have in next release of log4j a > complete system Event/lIstener for : > > - Listening to appender events (AddAppenderEventListener , > RemoveAppenderEventListener, fireAppenderEvent) > > - Listening to log Events (AddLoggingEventListener, > RemoveLoggingEventListener, fireLoggingEvent) > > > > For instance, it could be interesting to listen to log events to know if a > log error was generated (Sometimes in > > Bad programming pratices, there is somewhere a try/catch block which is not > rethrowing exception catched). > > > > I know that a possible workaround for this problem is to create a subclass > of NullAppender and listen to events passed to appenders. > > > > Any Ideas ? > > > > S�bastien --------------------------------------------------------------------- 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]
