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 (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C826E1.22162ADF"
Subject: autoDeploy attribute behavior
Date: Wed, 14 Nov 2007 09:09:36 -0800
Message-ID: <927B303FE145774289C9CC3312881CC5492C17@IMS-EMAIL.ims.dom>
Thread-Topic: autoDeploy attribute behavior
Thread-Index: Acgm4SIIdQ67edtUQfWImAiGwiHl2A==
From: "Beth Hechanova" <bhechanova@imsconsultants.com>
To: <users@tomcat.apache.org>

------_=_NextPart_001_01C826E1.22162ADF
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

=20

I have a war file that I do not want to be automatically deployed when
it is copied to the webapps directory, so I have set the autoDeploy
attribute in server.xml to false.  However, I would like that new war
file to be expanded when tomcat is restarted, but that does not seem to
be the case.  If I delete the corresponding directory before restarting
tomcat, then obviously I can see the updated changes on the website. =20

=20

Is there another configuration parameter to use that will define the
behavior I'm looking for -=20

*	Allow for a new war file to be deployed, but do NOT want those
changes to take affect
*	Reboot tomcat
*	Changes in new war file can be seen

=20

Thanks,

Beth


------_=_NextPart_001_01C826E1.22162ADF--