DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34614>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34614 Summary: Differentiate between global JAR files and those used by webapp config.xml Product: Tomcat 5 Version: 5.5.9 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] To my understanding, any JAR file placed in common/lib becomes global and all webapps automatically see them in their classpath. As well, it seems that a webapp's configuration file (conf/.../*.xml) requires a specific JAR in its classpath -- such as a DB driver -- then it must be located in the global JAR repository as well. I am asking that we differentiate between JARs referred to by configuration files and those that are *meant* to be global across all webapps. The problem is that all too often we are forced to place JAR files in common/lib because our configuration files refer to them but then this causes conflicts between applications. One application might require one version of the JAR while another might require another -- or some application shouldn't see a certain JAR at all on its classpath because then it might decide to use it when we don't want it to. Anyway, I think you get my point. Is there a trivial workaround for this problem? If not, any idea on how to solve it? Thank you, Gili -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
