Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C89451.B8653F64"
Subject: Deleting context xml files
Date: Tue, 1 Apr 2008 16:40:08 -0700
Message-ID: <A956112F7A72064288A172CE5EB07ABC02EA933F@EX03.asurite.ad.asu.edu>
Thread-Topic: Deleting context xml files
Thread-Index: AciUUbcXeSv3fQY2SsK4dv7/G8LViA==
From: "Albert Wold" <alwold@asu.edu>
To: <users@tomcat.apache.org>

------_=_NextPart_001_01C89451.B8653F64
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hello,

Recently I have been using per-context XML files in
/usr/local/tomcat/conf/Catalina/localhost to define environment specific
information for my webapps.  That way, when I move a war file through
the cycle of dev/qa/production, I can be sure that I'm running the same
code, and don't have to fiddle with settings inside the war file.

=20

I'm not sure when it started happening, but during development it seems
that tomcat is deleting the context xml files at seemingly random times.
I think it has something to do with the undeploy/redeploy process that
happens when the war file changes.  It seems particularly common when
there is a startup error in my app, but it is always when something in
the webapp changes.  Has anyone else experienced this?  I have been
using tomcat 6.0.14, but I just upgraded to 6.0.16 to see if that helps.

=20

Basically, I'm wondering if I'm doing something against proper practice
right now that is causing this or if there is some sort of bug in
tomcat.  I am using maven, so I have less control (probably partly
because I a haven't figured it out fully yet) over the copying of files
than I did with ant and I'd be interested to hear what other people are
doing for dev deployment when using context xml files.

=20

-Al


------_=_NextPart_001_01C89451.B8653F64--