I created and checked in new listener interfaces LoggerRepositoryEventListener and LoggerEventListener. You can review.
I then went ahead and modified LoggerRepository to deprecate the current addHierarchyEventListener() method and to add new methods to add/remove the new listeners. I then went ahead a started to modify Hierarchy to support the new listeners. Everything is straight forward until I get to fireAddAppenderEvent() and fireRemoveAppenderEvent() methods. Both of these take Category as input parameters, so I get a compile error when I try to pass it to the LoggerEventListener methods that require a Logger. Also, fireAddAppenderEvent() is actually defined in the LoggerRepository interface. Why? Seems like that should be a private/protected method of Hierarchy to me. Can we look at upgrading Hierarchy to use Logger instead of Category? I'm guessing that it will affect the current interface quite a bit. Ceki, I think it will require you to look into it as this has the potential to break lots of things. I have not checked in my LoggerRepository or Hierarchy changes as doing so will break the build. I have enclosed them with this email if it will help. stuck, -Mark
Hierarchy.java
Description: Binary data
LoggerRepository.java
Description: Binary data
-- To unsubscribe, e-mail: <mailto:log4j-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:log4j-dev-help@;jakarta.apache.org>
