Hi, I agree with Remy. These proposed "solutions" are actually more problems. If it were up to me there'd be two classloaders repositories: one for Tomcat (server/lib), and one for each webapp (WEB-INF/lib). No shared, no common, no WEB-INF/classes. But then again, it's not just up to me ;)
Yoav Shapira http://www.yoavshapira.com >-----Original Message----- >From: Remy Maucherat [mailto:[EMAIL PROTECTED] >Sent: Thursday, October 28, 2004 9:45 AM >To: Tomcat Developers List >Subject: Re: Two modest proposals about common\lib > >Tim Funk wrote: > >> I've been pondering something similar. (I just never got around to >> vocalizing it) My preference is to introduce common/usr_lib (and >> server/usr_lib)(This name is horrible, but you get the idea) >> >> The usr_lib dirs would be in the same classloader as common/lib (or >> server/lib) and would contain user specific jars. This way users would >> not have to add/change jar files in common/lib when upgrades occur. > >More problems, more confusion. Bad idea. > >People can use the properties file to tweak the classloaders if they >need it. > >Rémy > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
