Another option would be to write your own appender which filters before creating the message and if it passes then sends it to a normal appender.
On 7/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
This is the kind of answer I was afraid of ;) But that is a very powerfull feature some of our (large) customers are asking for very loudly: it gives both debug messages and good-enough performance for live systems. Sure I could do it myself, but then that would not apply to already existing log4j-compliant code :( I'll ask to the dev mailing list, just in case... Thanks for your help, Vincent. >-----Original Message----- >From: ext Javier Gonzalez [mailto:[EMAIL PROTECTED] >Sent: Wednesday, July 19, 2006 5:08 PM >To: Log4J Users List >Subject: Re: High performance filters > >On 7/19/06, [EMAIL PROTECTED] ><[EMAIL PROTECTED]> wrote: >> I hope this is clear enough :) > >It is, and your problem looks very non-trivial :) > >To me, it looks like you need to implement your own filtering >before invoking buildDebugMessage(), since to access the log4j >framework you need to pass an object (whose construction is >what you want to avoid). > >-- >Javier González Nicolini > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- James Stauffer Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
