logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: HierarchyEventListener Question
Date Mon, 07 Oct 2002 12:04:11 GMT
At 22:34 06.10.2002 -0700, mwomack@apache.org wrote:
>I am continuing the work on plugins.  The plugin knows what repository it is
>attached to, but the repository does not know about the plugin.  An issue
>with this is that when the repository is shutdown, then the plugin should be
>informed so that it too can shutdown.  One way for the plugin to be informed
>of the repository shutdown is to register a HierarchyEventListener with the
>repository via the LoggerRepository.addHierarchyEventListener() method?  Is
>this the right way to approach it?

Yes, definitely.

>  If so, I will need to add some new
>methods to the HierarchyEventListener interface, specifically
>shutdownEvent().  The Hierarchy class will also need to be modified to call
>this new method on registered listeners when shutting down.  Currently
>existing classes that implement HierarchyEventListener will also be
>affected, since they will not have the new methods implemented.

I think we have to put much more effort into the definition of the 
hierarchy life cycle. The current definition of HierarchyEvent is patently 
lacking. We can either add methods to HierarchyEvent or alternatively add 
new event types. The Monitoring API of JMX is also worth a look.

>advice or suggestions?


TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793

To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>

View raw message