First, shared libraries are evil. What do you think causes "DLL Hell" for Windows sufferers? If you're really that short on disk space, Best Buy sells hard drives for about a dollar a gigabyte. It doesn't save you any RAM, and doesn't save you any CPU cycles ... it only saves you some disk space.
Second, consider what happens when all your applications depend on a single shared library, and that library releases a new version. At what point can you safely upgrade the library? Only after you've verified each and every application on the server. If, like most Java projects, you have several libraries in your dependency graph, how many upgrade cycles can occur before you are hopelessly locked down? Put your libraries in your application-specific class path and don't allow other applications to foist their version incompatibilities on you. You'll be much happier in the long run. we-dont-need-no-stinkin-shared-libs-ly y'rs, +Mitchell > -----Original Message----- > From: Rasputin [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 13, 2003 2:39 PM > To: Struts Users Mailing List > Subject: Re: Struts1.1 message resources ???en_CA.version??? > > > * David Graham <[EMAIL PROTECTED]> [0344 18:44]: > > Is struts.jar one of those jars? If so, it's not > surprising that there are > > problems finding the properties file. > > Sorry if this is a dumb question, but why? > > Is it a general rule that struts.jar shouldn't be in tomcat's > classpath? > What about $CATALINA_HOME/common/lib/ ? > > -- > She is not refined. She is not unrefined. She keeps a parrot. > -- Mark Twain > Rasputin :: Jack of All Trades - Master of Nuns > > --------------------------------------------------------------------- > 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]
