applied. Thanks.
Chris, would you mind taking a crack at some tests for these
additions? We're a little thin on tests in the T2 codebase
and you did a nice job in the patches to stratum.
Thanks again.
-Eric
On Tuesday, April 2, 2002, at 02:05 PM, Chris Kimpton wrote:
> I chose to effectively backport what
> torque and fulcrum do, that is, use log4j properties directly, for
> example:
>
> # An example configuration for using Log4Java, with log4j properties
> inline
> # The category name - at the end of this line - needs to match the
> logging facility name - the first log4j.
> # need this rootCategory entry to capture the torque/fulcrum etc
> logging
> services.LoggingService.logforj.log4j.rootCategory = DEBUG, logforj
> # need this category entry for the actual jetspeed logging (I don't
> know why it doesn't get covered by the root category!)
> services.LoggingService.logforj.log4j.category.logforj = DEBUG,
> logforj
> services.LoggingService.logforj.log4j.appender.logforj.file
> =${webappRoot}/WEB-INF/log/jetspeed_log4j.log
> services.LoggingService.logforj.log4j.appender.logforj =
> org.apache.log4j.FileAppender
> services.LoggingService.logforj.log4j.appender.logforj.layout =
> org.apache.log4j.PatternLayout
> services.LoggingService.logforj.log4j.appender.logforj.layout.conversionPattern
> = [%d{ABSOLUTE} %-5p] %m%n
> services.LoggingService.logforj.log4j.appender.logforj.append = false
> services.LoggingService.logforj.className=org.apache.turbine.services.logging.
> Log4JavaLogger
> services.LoggingService.logforj.level=DEBUG
>
> This gives the full flexibility of log4j - in particular allows for
> merging the torque et al logs into one, while keeping the turbine
> TR.props configuration of it.
>
> This patch relies on the stratum patches submitted earlier - in
> particular for the interpolate additions relating to getStringArray
> and subset.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
