At 00:34 18.10.2002 +0100, you wrote:
Isn't log4j finished with the AuditObject once the
call to ObjectRenderer.doRender(Object) call has been
made with that object as the parameter? I was
thinking that at that point, the AuditObjectRenderer
could return the AuditObject to the pool.
Usually t
Isn't log4j finished with the AuditObject once the
call to ObjectRenderer.doRender(Object) call has been
made with that object as the parameter? I was
thinking that at that point, the AuditObjectRenderer
could return the AuditObject to the pool.
Or is there other stuff going on within the framew
You can't pool AuditObjects because you can't know when log4j has
finished using them. You'd need to modify log4j code such that when
the AuditObject is really written to the output media the AuditObject
is returned to the pool.
If there were a standard pooling API log4j could have done it for
I'm thinking that perhaps "audit" is not the right
term for what we're doing.
We have to collect this data (business requirement);
the data will be aggregated and reported with a
dedicated reporting tool (probably CrystalReports).
We also have to provide the ability to drill down to
detailed da
At 08:12 16.10.2002 +0100, you wrote:
>We are soon to be doing almost exactly that kind of
>thing on our project, for the purposes of auditing.
>
>We would like to use custom "AuditObjects" and log4j
>as the audit trail API. For the implementation of the
>recording of the audting, we'd have custo
IL PROTECTED]>
> To: "Log4J Users List"
> <[EMAIL PROTECTED]>
> Sent: Monday, October 14, 2002 9:33 PM
> Subject: Re: Formal parameter ideas?
>
>
> > What about encapsulating your formal parameters in
> a
> > single object, then having a l
al Message -
From: "Shorn Tolley" <[EMAIL PROTECTED]>
To: "Log4J Users List" <[EMAIL PROTECTED]>
Sent: Monday, October 14, 2002 9:33 PM
Subject: Re: Formal parameter ideas?
> What about encapsulating your formal parameters in a
> single object, then having
What about encapsulating your formal parameters in a
single object, then having a log4j object renderer to
format that object?
Something like this:
FormalParams fp =
new FormalParams("johndoe","14.95","software");
mycartlog.info(fp);
Doesn't stop people from logging whatever they want,
but w
I want to impose some formal parameters on logging. By that I mean,
mycartlog.info("johndoe","14.95","software"); etc, and stamp that into the
log in a known (and more parseable) format.
I wish to reduce the risk of someone making a logger and not formatting
correctly so this idea came up. I cou
