-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck,
Caldarale, Charles R wrote: >> From: Christopher Schultz [mailto:[EMAIL PROTECTED] >> Subject: Re: What changes require a redeploy? >> >> I think these resources are automatically "watched". You can certainly >> configure others. > > This is dependent on the reloadable attribute of the <Context> element; Thanks for pointing this out. It occurred to me that this fact was self-evident, but the OP is asking about things like this. >> You can (I think) avoid the work directory entirely by specifying >> unpackWARs="false" in your <Host> configuration. > > No, this forces use of the work directory; setting unpackWARs to true > allows the unpacking to occur in the appBase directory. Nothing is run > directly out of a .war file. Thanks for pointing this out as well: a WAR file is always exploded... the only question is where it will actually end up going. It looks like you can't avoid the work directory at all, since... > The work directory is also used to hold translated and compiled JSPs and > serialized sessions. ...these types of things may or may not exist in your WAR file, so use of the work directory is unpredictable. Tomcat then always creates that directory just in case? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGS2fX9CaO5/Lv0PARApUNAKCYtUKluqjcyGa5nFZYUg1vZupcMgCaAg96 3vTVrQF96BRpLi03MgoGS+o= =/4E0 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
