On 7/1/07, Thomas Vandahl <[EMAIL PROTECTED]> wrote:
Nathan Bubna wrote:
> 1) the AvalonLogChute class first tries to get its Avalon Logger via
> Heirarchy.getDefaultHeirarchy().getLoggerFor(<some logger name>).
> This <some logger name> is null by default but can be set to a valid
> logger name via the "runtime.log.logsystem.avalon.logger" property in
> your velocity.properties. So, it would seem that if you create a
> logger for <some logger name> in the default log heirarchy and then
> start up your VelocityEngine using the property:
>
> runtime.log.logsystem.avalon.logger=<some logger name>
>
> then the AvalonLogChute should use your Logger of choice. this
> appears to be the intended pattern by those who first designed the
> AvalonLogChute
I couldn't get this to work. Somehow, the name of the logger is not easy
to determine. But even if I set the logger name manually, I see the log
messages going to the console instead of the log file. So I chose...
> 2) you can create your own LogChute implementation that wraps your
> Logger and add an instance of this class you created directly to the
> Properties used to init() your VelocityEngine under the key
> "runtime.log.logsystem". Velocity's LogManager always first checks
> the configuration properties for LogChute under that key before trying
> any other means to get a LogChute.
great. :) thanks for reporting back!
Bye, Thomas.
---------------------------------------------------------------------
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]
