Lucas, We can certainly add a reference on the log4j pages (though Ceki might have to do it since I do not have the Anakia tool set up on my machine right now). You might also want to announce this tool on the log4j-user email list.
Also, something else that has been bandied about as a neat feature is the ability to instrument the code with debug statements to mark when a method is entered/exited. For a future version, you might want to look into adding this as well. thanks, -Mark > -----Original Message----- > From: Lucas Bruand [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 17, 2003 1:51 PM > To: [EMAIL PROTECTED] > Subject: Announcement: Just4log, a performance-oriented postprocessor > for Log4j > > > > > Hello, > > I wanted to advertise Just4log > (http://just4log.sf.net/), a apache-licensed project that's > highly related to Log4j: > > In the Log4j manual, Ceki Gülcü speaks about the "The > method invocation involves the "hidden" cost of parameter > construction." > ( refer to http://jakarta.apache.org/log4j/docs/manual.html > section "Logging performance when logging is turned off") > > That led me to the thought that a postprocessor acting > on the bytecode would be interesting to write. (a > preprocessor is definitely not java) Dada, Just4log was born: > it is a anttask that transforms the bytecode to remove the > hidden cost of parameter construction. > > Just4log uses Jakarta BCEL to operate on the bytecode. > > Do not hesitate to mail me any question regarding this project. > Cheers, > Lucas > > PS: Is it possible to reference Just4log on the Log4j website ? > > Just4log > http://just4log.sf.net/ > > > --------------------------------------------------------------------- > 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]
