On Thursday 20 January 2005 05:48, Jacob Kjome wrote: > 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.
Not necessarily true. IMHO, A container should NOT provide/expose anything beyond the 'explicit requirements' to the contained applications. Everything else quickly creates a mess. Unfortunately, there seems to be an entropy going on "out there", where stuff slowly makes its way into the system classloader and other shared classloader hierarchies, and applications start relying on that these shared resources 'exists', and don't bundle them. I don;t know the internals of Tomcat now, but once upon a time, the whole point of Catalina was exactly the above, and not a "Child First Behavior". If CFB is in place in Tomcat, it is because of this bad entropy, and Tomcat is then indirectly adding to it. Whether Log4J has added its share to the current state, I will leave unsaid... :o) Well, well... Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
