At 06:21 PM 1/13/2005, Ionel GARDAIS wrote:
+1
Its also make log4j lighter when shipped into WARs.
One of the important features in 1.3 is that you no longer have to
ship log4j.jar in WARs. The idea is to place log4j.jar in your
server's common/lib or equivalent. Log4j will still be able to treat
the logging output generated by each web application separately. In
the web.xml descriptor for your web-application, just add a log4j
specific <env-entry>. This entry gives a name to your application's
logging context which can be configured separately from all other
contexts.
This approach gives a lot more control over the way logging is
configured. For example, merging the logs of two applications is as
easy as giving their log contexts the same name.
ionel
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
