> The idea is to have listeners attach to the hierarchy (or logger > repository). Each time a logger changes its level, or appenders are > attached/detached from it tells its hierarchy to notify the listeners. > (Listeners are per hierarchy not per logger). > > Events of interests are: > > - hierarchy threshold change > - logger creation, > - logger change (level, appender) > - appender change (Appenders tell the hierarchy to notify listeners. Thus, > appender have to have know the hierarchy where they belong. to It is up to > the appender to decide when to tell the hierarchy to notify listeners.) >
Ahh, I see, so will the sequence be something like:
* call to Logger.setLevel(...) * Logger informs it's repository of change (PropertyChange?) * Repository notifies listeners of change.
Yes, absolutely.
Paul
-- Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp import org.apache.Facetime;
ApacheCon US 2003, 18-21 November http://apachecon.com/--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
