Another way (as I do it in my project now) is trough a common logger wrapper just as Commons Logging.
I use a slightly modified version of the Avalon wrapper for logging in my framework, which enables me to use any of the "3 BIG" logging APIs. So, I implemented a new Velocity logging adapter for such logging interface which I set programmatically. Whatever logger implementation I am using, is used for Velocity too. Have fun, Paulo Gaspar > -----Original Message----- > From: Tomasz Pik [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 31, 2002 12:01 PM > To: Jakarta Commons Developers List > Subject: Re: [Logging] [VOTE-REDUX] Commons Logging 1.0 Release > > ... > > 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]>
