On Sun, Oct 24, 2004 at 11:00:38PM -0400, Steven J. Owens wrote: : I'm interested in hearing how people are dealing with : configuration management issues. : : We've been running into some problems with JSP recompiles, : particularly when the changed JSP is an included JSP. : [snip]
Simplify your life: rely on formal releases instead of updating piecemeal (e.g. tweaking a JSP on a live site). In theory, you should be able to automate the following: 1/ pull a release label from source code control 2/ build the code, package it up into a WAR file (this includes JSP precompiles) 3/ push the new WAR out to your Tomcat server(s) 4/ stop Tomcat, clear the work dir, restart Tomcat For rollback purposes, you'll want a step 3.5: stash the original WAR file somewhere. : This reminds me of another question; I'm beginning to wonder if : we wouldn't be wiser to use a dozen separate tomcat installations. I'm all for app separation. Even if they stay the same/similar for their entire lifetime, management of separate apps is easier. Either that, or find some way to deploy a single app but use creative branding so each customer gets their own look'n'feel. : I : know that in theory using the same tomcat installation for multiple : webapps is supposed to be "standard", Says who? -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
