Tim Colson said:
> Geir said:
...
> > You can't fix the usage pattern, though. I've tried...
> I don't claim a deep understanding...but on the surface I'm seeing
> LogSystem and C-L as similar beasts, similar usage. So long as I can
> write logThingy.error("Boom!") - I'm pretty happy. Albeit, I'd want
> Nested Diagnostic Contexts from log4j too... they are quite nice for
> pushing the session ID into every log mesg from a servlet.)
if Velocity switched from LogSystem to c-l, there still wouldn't be a darned
thing stopping you from using NDC in your app. see, you may need fancy stuff
like that, but Velocity itself doesn't. c-l has all the features i can ever
imagine Velocity needing. (it certainly has more than LogSystem!!). so, if
Velocity uses c-l, then you just point c-l to use log4j (which your code uses
directly), and everyone is happy!
well, except Geir, who feels we should have to configure logging separately
for each and every component/library in our applications. ;)
Nathan Bubna
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
