> On windows my issues appears to be that the context.xml from the > auth.war is being cached inside tc/conf/Catalina/localhost/...
"cached" is not the right word. It is how deployment mechanism works in tomcat. The presence of <app_name>.xml in tc/conf/Catalina/localhost/ means that you application has been successfully deployed. Removal of the file means that you trigger the auto-deployment mechanism for your application. See http://tomcat.apache.org/tomcat-6.0-doc/config/context.html for details (look for "$CATALINA_HOME/conf/[enginename]/[hostname]/" there) As for your problem I understand, that you have database connection in one application, and are reusing it from another one? Is it just that? It it is the case, I suggest to move connection pool configuration from application context.xml into GlobalNamingResources of server.xml, see http://tomcat.apache.org/tomcat-6.0-doc/config/globalresources.html In application context.xml you will specify a local synonym for this global resource using ResourceLink element. I hope this will help you. Best regards, K. 2008/1/18, Fu-Tung Cheng <[EMAIL PROTECTED]>: > Hi, > > I have two war files. One is an authentication war and the other is setup to > use the authentication war via the servlet context.xml mechanism. > > On windows my issues appears to be that the context.xml from the auth.war is > being cached inside tc/conf/Catalina/localhost/... and that on the 2nd > startup it tries to test the connection before the war that is the connection > has loaded. I've solved this temporarily by deleting this directory before > startup. > > Does anyone know of a better way to do this? I am using tomcat 6014. > > Thanks, > Fu-Tung > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
