> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, July 28, 2001 6:45 PM
> 
> On 7/28/01 12:42 PM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote:
> 
> > You find the logging stuff at the org.apache.velocity.runtime.log
> > package. Does it have to be much less simpler than this?
> 
> It's not flexible enough and it just duplicates what log4j does
> already. For example using log4j you could easily make logs for
> each directive if you wanted, or for each resource loader if
> you wanted. You can log information in any way you wish and it
> is completely configurable from a properties/xml file.

You can still let the log4j to be configured the way you want.

And being able to log per directive or per resource loader just depends 
on passing extra information to the adapter, which can be used or 
ignored by the adapter depending on the capabilities of the log system
that is plugged in.


Ok, it is not sooooo simple anymore, but it still allows to keep the
project log agnostic and allow it to be used in very lightweight 
solutions (one can even use a NulLog adapter).

IMHO, this flexibility is very important and compensates the work of 
the adapter thing.


Have fun,
Paulo Gaspar

Reply via email to