| Michael Watzek 2005-09-01, 5:45 pm |
| Hi,
the current logging configuration of TCK works fine for implementations
using Log4J logging. In "log4j.properties" vendors may specify appenders
and assign these to loggers, e.g.:
# appenders
log4j.appender.vendor=org.apache.jdo.tck.util.TCKFileAppender
log4j.appender.vendor.File=vendor.txt
log4j.appender.vendor.layout=org.apache.log4j.PatternLayout
log4j.appender.vendor.layout.ConversionPattern=%d{HH:mm:ss,SSS} (%t)
%-5p [%c] - %m%n
# loggers
log4j.logger.vendor=INFO, vendor
This ensures that vendor specific logging files are generated as
"target/logs/<timestamp>/<database><identity
type><configuration>-vendor.txt".
Attached you find a patch for review that implements the same feature
for vendors using JDK1.4 logging. In "logging.properties" vendors may
specify handlers and loggers, e.g.:
# loggers
vendor.level = INFO
# default handlers
handlers = org.apache.jdo.tck.util.TCKFileHandler
# handlers
org.apache.jdo.tck.util.TCKFileHandler.fileName = vendor.txt
org.apache.jdo.tck.util.TCKFileHandler.level = FINEST
This ensures that vendor specific logging files appear in the same
directory with the same naming pattern as in the log4j case.
Regards,
Michael
--
-------------------------------------------------------------------
Michael Watzek Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
-------------------------------------------------------------------
|