Your point is well taken and log4j domains to be introduced in log4j 1.3 will provide an very solution you mention. I would also like to point our that you gave the TRACE level a higher weight than DEBUG, i.e. you chose TRACE > DEBUG, but many developers assume DEBUG > TRACE.
At 08:39 AM 10/19/2003 +0200, Tom Eugelink wrote:
IMHO, for as far as it matters, I do feel that one debug level is somewhat coarse. My debug information often has two levels of granularity. The main level being program flow and decision logic, the second level is logic support information like SQL statements, variable content, etc.
Ofcourse it is possible to add a second log4j category to handle the latter output, but that is somewhat overdone. Adding a "program logic marker" to highlight the logic output is an option.
But personally I'd feel for adding a "trace" level between info and debug, for showing program logic to get closer to the place where stuff goes wrong and then switch to debug.
INFO: show program configuration info, etc TRACE: show program logic and flow DEBUG: show logic explanation / reasoning
Tom
-- Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp import org.apache.Facetime;
ApacheCon US 2003, 18-21 November http://apachecon.com/--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
