Yes, you get a Logger and then call Logger methods such as debug() or error()
Example basically from
Log4j Manual:
A simple way to configure log4j is using a properties (or xml) file. The first time Logger.getLogger() is called log4j looks for either log4j.xml or log4j.properties on the classpath.
The manual also has sample properties files.
Then you said you wanted to turn off debug logging. Log4j uses Levels, if you set a logger's level to WARN, then it will log messages that are at level WARN or more severe (see manual for more or better explanation)
Suppose we are no longer interested in seeing the output of any component belonging to the com.foo package. The following configuration file shows one possible way of achieving this.
log4j.rootLogger=DEBUG, A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
# Print the date in ISO 8601 format
log4j.appender.A1.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
# Print only messages of level WARN or above in the package com.foo.
log4j.logger.com.foo=WARN
If you want a more in-depth manual than what is available at the URL I posted for log4j manual, try
The complete log4j manual commercially ($) available in pdf.
[ March 16, 2005: Message edited by: Carol Enderlin ]
[ March 16, 2005: Message edited by: Carol Enderlin ]