Quoting Ceki Gülcü <[EMAIL PROTECTED]>: > At 03:09 PM 1/17/2005, Endre Stølsvik wrote: > >On Thu, 13 Jan 2005, Ceki Gülcü wrote: > >| > >| One of the important features in 1.3 is that you no longer have to > >| ship log4j.jar in WARs. > > > >What if the servlet container does not provide log4j? It isn't exactly > >mandated by the spec. > > No log4j is not mandated by the servlet spec. :-) > > Some of the reasons for placing log4j.jar in the server's classloader > were mentioned in my post dated Fri, 14 Jan 2005 17:24:45 +0100. >
of course if you have the authority to add log4j.jar to the server's classpath, why wouldn't you have the authority to add other jars there as well? > >And what if I use log4j 1.3.5, that have this nice new feature, while the > >servlet container provides the old and boring 1.3.1? > > This is an important point to keep in mind. First, we ensure BWC so > that there won't be any drawbacks for replacing the containers copy > with the latest version, say 1.3.5 in your example. > > If 1.3.5 can be provided by the container and if your web-application > absolutely requires log4j version 1.3.5, then you can still bundle > version 1.3.5 of log4j.jar with your web-application. One disadvantage > of this approach it that your web-application's logging will be > invisible to the rest of the container. > Ceki, you *always* assume that child-first classloading behavior will be available, and this just isn't always true. In fact, Java2 classloading behavior is the default for pretty much every appserver I can think of other than Tomcat. Some provide the *option* to trigger child-first behavior, but in many cases it is not very well supported. Tomcat is the only real example of this being a viable option. > >Anyways, as long as you can bundle what you want with your app, I'm happy. > > Bundling log4j.jar with your web-app will still be an option. However, > it will no longer the *only option. > ...Under Tomcat Jake > >Endre > > -- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
