At 06:48 AM 1/20/2005, Jacob Kjome wrote:
I don't understand what you mean here? If the server provides only Java2 classloading behavior, no matter what you bundle with your app, you are at the mercy of the server version. Backwards compatibility would certainly be key in keeping apps running, but the discussion was the webapp controlling its own version of Log4j, and that is not possible in this example, unless you are the server admin (or know the server admin well). This is why I said "....Under Tomat". Only server implementing child-first classloading behavior could allow you to bundle log4j.jar with the webapp and count on that version being used rather than the server version.
You are quite right.
Jake
-- 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]
