logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Womack <mwom...@bevocal.com>
Subject RE: automatic trace insertion
Date Mon, 17 Dec 2001 22:13:41 GMT

This would be really cool.  If you do it, it would be cool to include it as
part of log4j as an optional tool.

Thinking about it, it would cool to control what classes are instrumented
via the configuration file.  That way one does not get noise from every
method of every class; only the ones you care about.  Or maybe you already
had that in mind.


-----Original Message-----
From: Scott Sanders [mailto:sanders@totalsync.com]
Sent: Monday, December 17, 2001 1:56 PM
To: 'Log4J Developers List'
Subject: RE: automatic trace insertion

I just looked at quilt (http://quilt.sourceforge.net).  It is a code
coverage testing tool, but it modifies the binary class files to insert
coverage auditing calls.  You could use what he has already done to do
the same type of thing.


> -----Original Message-----
> From: bchen@porivo.com [mailto:bchen@porivo.com] On Behalf Of 
> Benson Chen
> Sent: Monday, December 17, 2001 1:57 PM
> To: log4j-dev@jakarta.apache.org
> Subject: automatic trace insertion
> Hi all,
> I'm interested in automatically inserting log4j trace 
> statements at the beginning of all methods and right before 
> the end of a method (return statement or thrown exception).  
> I'm presuming most people have worked on projects with 
> extensive class libraries and it would be great if there was 
> a class parser that could intelligently insert log4j 
> statements automatically.  If there isn't anything out there 
> like that, does anyone know of a java class parser that can 
> be used to do this sort of thing?  Thoughts or ideas?  Thanks!
> --
> Benson Chen
> Director of Software Engineering
> Porivo Technologies, Inc.
> Phone: (919)806-0566x12
> E-Mail: benson@porivo.com
> "Measuring end-to-end Web performance"
> --
> To unsubscribe, e-mail:   
> <mailto:log4j-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:log4j-dev-help@jakarta.apache.org>

To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>

To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>

View raw message