I would advise to not place app jars in common as it is used by TC Internals here is why (straight from TC5.5. Doc) a.. Common - This class loader contains additional classes that are made visible to both Tomcat internal classes and to all web applications. Normally, application classes should NOT be placed here. All unpacked classes and resources in $CATALINA_HOME/common/classes, as well as classes and resources in JAR files under the $CATALINA_HOME/commons/endorsed, $CATALINA_HOME/commons/i18n and $CATALINA_HOME/common/lib directories, are made visible through this class loader. By default, that includes the following: a.. commons-el.jar - Jakarta commons el, implementing the expression language used by Jasper. b.. jasper-compiler.jar - The JSP 2.0 compiler. c.. jasper-compiler-jdt.jar - The Eclipse JDT Java compiler. d.. jasper-runtime.jar - The JSP 2.0 runtime. e.. jsp-api.jar - The JSP 2.0 API. f.. naming-common.jar - The JNDI implementation used by Tomcat 5 to represent in-memory naming contexts. g.. naming-factory.jar - The JNDI implementation used by Tomcat 5 to resolve references to enterprise resources (EJB, connection pools). h.. naming-factory-dbcp.jar - Jakarta commons DBCP, providing a JDBC connection pool to web applications. The classes have been moved out of their default org.apache.commons package. i.. naming-java.jar - Handler for the java: namespace. j.. naming-resources.jar - The specialized JNDI naming context implementation used to represent the static resources of a web application. This is not related to the support of the J2EE ENC, and cannot be removed. k.. servlet-api.jar - The Servlet 2.4 API. l.. tomcat-i18n-**.jar - Optional JARs containing resource bundles for other languages. As default bundles are also included in each individual JAR, they can be safely removed if no internationalization of messages is needed.
M- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. ----- Original Message ----- From: "Darren Hall" <[EMAIL PROTECTED]> To: "'Tomcat Users List'" <users@tomcat.apache.org> Sent: Tuesday, September 19, 2006 12:09 PM Subject: RE: cannot load jdbc driver?? >> They will be accessible by your war file code. You do not need the jar >> in both places. Only common/lib > > No no. I understand that it will be available to my code (since the app > server will put the jar in my classpath), but it means I can't deploy > ojdbc14.jar with my war any longer. Correct? > > -D > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
