I just want to make clear that I DO UNDERSTAND that filters, by their nature and implementation in log4j, are chainable, etc. I think this aspect is not fully understood by many of the log4j users, so I am trying to create a base class that exposes this functionality in a way that helps in the understanding, while also creating a set of useful filters.
Just so it is clear. I'll check in something tomorrow night and then start building useful filters on top of it after that. -Mark > -----Original Message----- > From: Mark Womack > Sent: Thursday, June 06, 2002 9:26 PM > To: 'Log4J Developers List' > Subject: RE: More Filter Thoughts > > > > 2) we find a different name for ChainableFilterBase, for example > > BasicFilter or FilterCore. > > > > The second option seems somewhat wiser because the basic notion of > > chaining filters is not being challenged. > > OK. I was just trying to capture the aspect that filters > subclassing from > this base class will be "chain-compatible". This is not true > of all filters > since it is dependent on the return values they choose to support. > > I'll come up with something. I might just support 3 properties: > chainPolicy which sets one of the 4 valid "chain-compatible" > return value > pairs; setMatchValue() and setNoMatchValue() which would > allow any filter > return value combination. You would use chainPolicy() or > setMatchValue() > and setNoMatchValue(). That way a filter could be used as > part of a chain > or by itself. > > I just want to get something in place. If people don't like it we can > change it or remove it altogether. > > -Mark > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
