logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41483] - PropertyFilter is not a filter, MapFilter not a filter
Date Fri, 10 Aug 2007 15:06:02 GMT
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=41483>.
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=41483


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Additional Comments From carnold@apache.org  2007-08-10 08:06 -------
I also would not be surprised if these "Filters" might not also carry over their modifications
into unrelated 
appenders.  For example, if you attached a filter to an appender attached to a specific logger,
then the 
modification might be seen by an unrelated appender attached to the root logger.

log4j 1.2 did not provide the methods that allowed mutation on LoggingEvents so these "filters"
were not 
backported to the extras companion.  Maybe the functional equivalent delegating appenders
could be 
added to "extras".

-- 
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


Mime
View raw message