Re: Context.xml being deleted
Thanks for the earlier replies. So after some more research it seems there is no way to tell tomcat that I don't want particular directories to be deleted on an application redeploy? Is this correct ? I have a forum application. When we update it we want to distribute a new war file (previously we updated all files individually). If we give out a new war file to our customers the images directory, the attachments directory and other directories that contain user uploaded data will be wiped out. Is there a solution to this dilemma? Sym links are are no - you'd have to remake them each time so still a lot of work. Any advice gratefully received. -- -Sam - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Context.xml being deleted
Hi all. The tomcat documentation says the following: If the web application is packaged as a WAR then /META-INF/context.xml will be copied to $CATALINA_BASE/conf/[enginename]/[hostname]/ and renamed to match the application's context path. Once this file exists, it will not be replaced if a new WAR with a newer /META-INF/context.xml is placed in the host's appBase. However, each time I upload a new WAR the existing context.xml gets deleted and replaced with the one inside the WAR file (which is just a default). So I lose all my configuration details. I have googled and it seems this is a common problem. Any help ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
