Hi, >Does this mean that servers like Weblogic JBoss are not properly >implementing >the servlet spec? For instance, Weblogic comes with Log4j in the classpath >because it uses Log4j for logging. Whether or not I add log4j.jar to >WEB-INF/lib, the one from the server is used. I believe there is an option >in >weblogic.xml to trigger child-first classloading behavior, but this is >certainly not the default. Either Weblogic is lying about it's claimed >support >for the servlet spec, or the servlet spec doesn't require this behavior. >The >latter would seem to contracict your statement. Can you clarify?
Those containers do support the Spec, but you have to flick a configuration switch to get strict Servlet Spec support configured. Instead, they opt for including commonly-needed libraries with the container and flipping the loading order. It's a fine way of going about things, especially if you document it well (which they do, at least Weblogic, e.g. http://e-docs.bea.com/wls/docs70/programming/classloading.html) and make it easy for users to switch, both programmatically and via a server admin console. I think Weblogic even lets you switch at runtime which is cool/interesting. So Weblogic and JBoss are not lying, they do support the Spec. And their out-of-the-box configuration is fine for many users. Remember the target market is different: Weblogic wants you to pay $$$ for consultants to set up the app, including libraries and classloading. Tomcat's users (or at least intended audience) is different. I know a couple of Weblogic consultants, and this PreferWebInfClasses (see above weblogic doc link) switch is among the first things they flick (so its behavior matches Tomcat) as a standard operating procedure. Yoav --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
