Tomcat deployment overwrites context.xml

Posted by Kristoffer on Server Fault See other posts from Server Fault or by Kristoffer
Published on 2010-03-25T21:58:56Z Indexed on 2010/03/25 22:03 UTC
Read the original article Hit count: 465

Filed under:
|

Hi,

I'm pretty new to Tomcat in general, so please point out if got anything wrong.

My question is regarding updates to already deployed apps, using the Tomcat manager. But first thing first. I'm using the META-INF/Context.xml for storing connection info for the database connections, so this is unique to every server the application is deployed to. I'm not sure if this is optimal but it's the only way I know.

So, when updating the application, it's important that this file doesn't get modified, because I don't want to have to go in and remake all changes every time I update my app.

For updating, I'm using the Tomcat Manager, and I've tried different approaches but everything seems to build on the process of undeploy, then deploy the new version. This way, the Context.xml gets removed/replaced by an empty Context.xml file.

So my question is basically, how do I update a running webapp, and at the same time having the Context.xml left untouched?

Btw, I'm running Tomcat 6.0.24.

© Server Fault or respective owner

Related posts about tomcat

Related posts about webapp