Paulo Gaspar wrote:
>>Well, we are deprecating that logger as it puts us (Velocity
>>devs) into the
>>position to have to support every possible app usage of log4j.
>>
>>The replacement just takes a category, so you can configure things in your
>>app as you want (not hope that we provided the configuration
>>options through
>>our properties...) and then have Velocity log directly to that...
>>
>
> Good move. That kind of logging config makes more sense on the
> application (or framework) level than on a library like Velocity.
Another way of configure Velocity for log4j:
1 one common log4j.xml config file for the servlet engine - it's
admin work to control log levels;
2 every app has its own prefix: 'example_app' for example
app know, that this app prefix is 'example_app';
3 Velocity (static initialization within every web-app) is configured
to get from Runtime 'xx.app_name' (xx to avoid problems) key and call
Category.getInstance(); with 'xx.app_name.velocity' within our
LogSystem implementation.
So we can configure different logging level for every application.
One (big for me) problem is that log4j during initialization
want to make instances of every renderers and layouts so I have
to put them into the servlet engine CLASSPATH.
Regards
Tomasz Pik
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
