On Thu, 2003-12-11 at 12:49, Scott Deboy wrote:
> Now the question of how to get chainsawappenderhandler to use the saved
> property via settingsManager. That looks a little more complicated.
>
Easy. We don't.
We can modify the Handler to have a getIdentifierExpression() + a setter
to make it
Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 5:35 PM
To: Log4J Developers List
Subject: RE: [chainsaw] chainsaw with multiple tabs...
> (spaces are removed after the event's values are retrieved)
> PROP.log4jmachinename - PROP.log4japp
>
I like this
> (spaces are removed after the event's values are retrieved)
> PROP.log4jmachinename - PROP.log4japp
>
I like this one. We can always work out a way to make spaces not
mandatory at latter stage if it's a pain right now.
> We could be smarter about it but that would require more complicated
>
stringtokenizer version.
We could be smarter about it but that would require more complicated
scanner logic.
Thoughts?
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 3:14 PM
To: Log4J Developers List
Subject: RE: [chainsaw] chainsaw with
> For example, for the way Chainsaw currently works, the only expression
> it's supporting is:
> PROP.log4jmachinename-PROP.log4japp
At a minimum we should at least convert over the ChainsawAppenderHandler
code so that it is configurable, rather than how we have it now (it's a
bunch of if()'s with
Here's my current thoughts on multiple tabs (mostly initialization time definition of
tabs):
We have the ability to look up logging event fields by keyword, using the
LoggingEventFieldResolver class.
This allows us to define expressions that can be resolved when an event shows up,
which can be
