tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Best practice application deployement
Date Tue, 07 Aug 2007 14:13:38 GMT
Hash: SHA1

Gerhardus, wrote:
> If the jsp gets compiled once after the war files get deployed then I would
> be willing for the server to be a bit less responsive for the 2 minutes or
> so that it takes for the application to deploy.

The problem is that JSPs are not compiled until they are accessed for
the first time. This means that your application will feel sluggish
until all popular pages have been hit at least once. Pre-compiling JSPs
simply avoids this compile-on-demand step (but, of course, increases
deployment time due to the time to pre-compile -- but if deployed
correctly, Tomcat's downtime is minimized).

> Assuming that you would deploy by copying files, copying one war file for me
> is simpler then copying a directory or larger collection of files.

If you use a tool like ant, or even a shell script (as you already do),
then you don't really have to worry about the complexity of the
deployment process: you just type "do it" and it gets done. Yes, it's
more complicated to work-out at first, but you may see a performance
improvement because of it.

I'm never a fan of premature optimization, though. If you're not having
any problems, don't change anything. Just keep this in mind for the
future, just in case you need it.

- -chris

Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla -


To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message