Hello,
I have hard time taming velocity log output.
My webapp uses log4j globally.
velocity.properties has the following:
runtime.log.logsystem.class = org.apache.velocity.runtime.log.Log4JLogChute
runtime.log.logsystem.log4j.category=velocity
log4j.properties:
log4j.rootCategory=INFO, LOGFIL
I would recommend using the log4j.xml configuration file, and put it
somewhere up high in your class path.
regards Malcolm Edgar
On 7/17/07, Joe Kramer <[EMAIL PROTECTED]> wrote:
Hello,
I have hard time taming velocity log output.
My webapp uses log4j globally.
velocity.properties has the fol
Hi Malcolm and Joe,
I have to echo Joe's comments: Velocity's behaviour with log4j and Commons
Logging is one of the things I find I find most irritating in general
development terms (as everything else is so nice and simple and works fine on
the whole).
I have _never_ been able to get logging
Joe/Chris--
I use log4j in some of my apps, haven't had much trouble.
Are you using Velocity 1.5? Velocity's logging behavior was cleaned up
substantially in the last release. The
"velocity.log" file is generated by the Avalon logkit, it shouldn't appear
if you use Log4J. Try removing "logkit
thanks, Will - I should probably go back and have another look at logging in my
default Velocity setup.
fyi/btw: I am using 1.5 ... I last thought about logging when I upgraded. I was
thinking "ah ha! this might fix that logging annoyance too!" - but it didn't :(
... so I left it alone for some
On 7/17/07, Joe Kramer <[EMAIL PROTECTED]> wrote:
Hello,
I have hard time taming velocity log output.
My webapp uses log4j globally.
velocity.properties has the following:
runtime.log.logsystem.class = org.apache.velocity.runtime.log.Log4JLogChute
runtime.log.logsystem.log4j.category=velocit
On 7/17/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Joe/Chris--
I use log4j in some of my apps, haven't had much trouble.
Are you using Velocity 1.5? Velocity's logging behavior was cleaned up
substantially in the last release. The
"velocity.log" file is generated by the Avalon logkit, i
On 7/17/07, Townson, Chris <[EMAIL PROTECTED]> wrote:
thanks, Will - I should probably go back and have another look at logging in my
default Velocity setup.
fyi/btw: I am using 1.5 ... I last thought about logging when I upgraded. I was thinking
"ah ha! this might fix that logging annoyance t
i'm not sure what you mean by "used by" here. Velocity shunts all log
messages through the LogChute of choice. if you tell it to use the
Log4jLogChute, it will either use a specific logger that you tell it
to use, or else it will create a default one. where in this should we
be looking at a lo
On 7/17/07, Joe Kramer <[EMAIL PROTECTED]> wrote:
>
> i'm not sure what you mean by "used by" here. Velocity shunts all log
> messages through the LogChute of choice. if you tell it to use the
> Log4jLogChute, it will either use a specific logger that you tell it
> to use, or else it will creat
Thanks, I got it working with log4j.
As you pointed out, the
runtime.log.logsystem.log4j.logger =
should be used instead of
runtime.log.logsystem.log4j.category =
in velocity.properties.
Thank you again!
On 7/18/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
On 7/17/07, Joe Kramer <[EMAIL PROTECTE
11 matches
Mail list logo
