Dale, Matt wrote:
I'm not sure what you're getting at here. The number of users are irrelevant to the classes. You should only use shared/classes if the classes have to be shared across web apps. Although this is not usually advised as it is good practice to keep web apps self contained.
WEB-INF/classes would take precedence over shared/classes but I still don't see what you are trying to achieve.
My understanding (I'm sure someone will correct me if i'm wrong) of the shared is that each class will be loaded into the classloader of each webapp so no memory would be saved, if you chose to use this area for sharing classes accross webapps.
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/class-loader-howto.html
I doubt that classes in shared lib are existing multiple times per webapp. I'm quite sure the exist per tomcat instance...
The difference is that common lib is available to both Tomcat and the webapps. Shared lib is not available to the Tomcat classes.
Typically one places the jdbc driver into common lib, because Tomcat needs that when using the JNDI pooling. If you just use old JDBC style it should work in shared lib or even web-inf/lib.
The interesting part is that shared lib is relative to catalina base, not catalina home, unlike common lib...
Cheers, Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
