DO NOT REPLY [Bug 9506] New: - Tool to debug appender duplications

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: More Filter Thoughts

Niclas, I find the idea of filter groups to be intriguing. As for configuration, setting the set of filters for a first level filter group would be fairly easy, but setting groups inside of groups would be impossible with the current DOMConfigurator. Maybe doable with the DigesterConfigurator Ce

RE: More Filter Thoughts

> You mean setMatchReturnVal(String val) where val is one of "ACCEPT", > "DENY" or "NEUTRAL". Same for setMismatchVal(). Correct? Yes. Sorry, I meant to use the filter return value as the argument. This is very much like the earlier filters I submitted, but it gets rid of the setCantMatchVal()

RE: More Filter Thoughts

At 10:07 29.05.2002 -0700, Mark Womack wrote: >Ceki, > >So, I think we are on the same page here. The RejectOnMismatch property is >one way to solve it, and it might be a better way. I don't know. I was >going to propose this: > >1) Leave the current set of varia filters as they are and possibl

RE: More Filter Thoughts

Ceki, So, I think we are on the same page here. The RejectOnMismatch property is one way to solve it, and it might be a better way. I don't know. I was going to propose this: 1) Leave the current set of varia filters as they are and possibly deprecate them in a future version. Create a o.a.l

Bug in getLogger(String, LoggerFactory)?

I'm using a custom LoggerFactory and not getting the expected behavior.  After taking a look at the source, the Hiearchy class's implementation of getLogger(String, LoggerFactory) doesn't account for the LoggerFactory producing logger's with different names.  The CategoryKey used to cache i

RE: Branches, was [cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw]

Sorry about that. I have made the changes to v1_2-branch. > -Original Message- > From: Ceki Gulcu [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, 28 May 2002 02:53 > To: Log4J Developers List > Subject: Branches, was [cvs commit: > jakarta-log4j/src/java/org/apache/log4j/chainsaw] > > > Oli

DO NOT REPLY [Bug 9435] - Chainsaw incorrectly loads priority (level) from XML log file

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Watchdog/Reconfigurator Nickel Tour

Mark, Thank you for taking the lead on this. Comments in line. At 22:24 28.05.2002 -0700, [EMAIL PROTECTED] wrote: >1) The purpose of the reconfigurator is to primarily "watch" or "monitor" a >"source" for some indication that said "source" has been changed or updated >with new/different config