DO NOT REPLY [Bug 37736] New: - LoggerEventListener's appenderRemovedEvent() and levelChangedEvent() methods are never called

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37736>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37736

           Summary: LoggerEventListener's appenderRemovedEvent() and
                    levelChangedEvent() methods are never called
           Product: Log4j
           Version: 1.3alpha
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: jessh@ptc.com


Despite registering a LoggerEventListener with a LoggerRepository/Hierarchy, the
appenderRemovedEvent() and levelChangedEvent() methods are never called.  This
is very frustrating and misleading.  [log4j 1.2 has the same issue with its
equivalent listener and event for appender removal...]

In log4j 1.3 at least this is due purely to the lack of a few lines of code in
Category to call the approach "fire" methods on Hierarchy.

I am attaching a patch which adds the necessary calls.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org