I would use wrappers, if at all, only for app or module wide special loggers
(like fatal error alerting etc.), and only
- if there is a special need to do something with the log event which cannot be
done using the log4j framework
- if some special initializing of the involved appenders is need
The loggers instance are being generated from a factory pattern in a j2ee
aplication and implements the log methods from wrapper class. Rather then
calling default logging methods from Logger (Catagory) Class.
Thanks.
James A. N. Stauffer wrote:
>
> A wrapper class (if you use something I sug
A wrapper class (if you use something I suggest that you use something that
is has been well-tested like commons-logging instead of writing your own)
allows you to switch logger implementations but probably prohibits the use
of some functionality. I would suggest using a wrapper only if you forese
