I understand that the tomcat standards specify that jar files with classes that are shared among more than one webapp should live in the "shared" directory.
However, for the application that I'm working on, there are some jars that are shared not only among tomcat-based webapps, but also, by other non-tomcat-based applications. These jars contain business logic for standard, company-wide calculations, and they are updated from time to time as these calculations evolve. And they have a standard "home" in which they live. I know that I could make copies of these classes or use symbolic links to get them into tomcat's "shared" directory, but this presents a deployment problem: if I keep copies, then tomcat's versions can (and often do) get out of sync with the official versions; if I use symlinks, they get stale and end up pointing to nothing, because the offical jars have names that reflect their version numbers. Furthermore, it's our company policy to have one and only one copy of each of these business-specific jars in our production environment. Ideally, I'd like to be able to tell tomcat's class loader to look in the home of these business-specific jar files in addition to the standard locations. Is there any way to do this? Thanks in advance. -- Lloyd Zusman [EMAIL PROTECTED] God bless you. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
