At 06:08 PM 1/13/2005 +0100, you wrote: > >This way, the user wishing to use SMTPAppender in her application can >place log4j-smtp.jar and mail.jar in her application's WEB-INF/lib >directory without the need to add any new jar files in ./common/lib. > >What do you think? >
Placing endorsed libraries in WEB-INF/lib is *not* recommended. In fact, Tomcat actively avoids loading at least some endorsed libraries from WEB-INF/lib (Not sure about all.... maybe Yoav can clarify?). By "endorsed", I mean stuff like javax.*, org.xml.*, org.w3c.dom.*, etc....
If you are making an argument for being able to drop mail.jar in WEB-INF/lib, I'm not buying it. The only reason I can see for the split-up of jars is for the developer who is writing an app that won't be running in a container and doesn't need the extras. I saw that Yoav mentioned that jar size is not a factor. You only have to look at the existence of the abomination that is commons-logging for evidence to the contrary. And then there is UGLI. Why have UGLI? Well, part is to abstract abstract logging implementations, but another major factor is that UGLI, at least in the minimal jar, is of small size. So, I think the breaking up of jars to create a smaller core jar is good for its own sake. But we still must have an all-encompassing jar so that we don't have to deal with, as Yoav says, "jar soup".
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]
