-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott,
[EMAIL PROTECTED] wrote: > Using your method of including the context within the application how do > you adjust for different environments (dev vs production)? Different > WARs? We use ant for deployment, and we have a "release type". The release type dictates the directory whence config files come, so our WARs are built to contain the context.xml file (as well as other files) appropriate for the target environment. > How we do it now is have a context.xml.default included in the > conf/Catalina/NameOfYourHostInServer.xml/ directory where the JNDI > datasource is defined. That way we can take the exact same WAR that was > deployed on dev and deploy it to production (since they point to > different DBs and thus have different datasources). My preference is to avoid making any changes at all to a stock Tomcat installation. Once installed (as root), the only change we make to the Tomcat installation directory is to make some files (web.xml, for instance) to be world-readable. Everything else is done as a non-privileged user with a separate CATALINA_HOME, config files, and deployment directory. We never mess with conf/Catalina or its contents. All applications are completely self-contained within their WAR files. This gives us the least resistance when it comes to deployment in any environment. Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGeA9Z9CaO5/Lv0PARAgz2AKCVYFX95xYNAj015BsCHJXE9gaY3ACeK5om Sqz5uM8YzHYOAorkUFmQCRM= =z40z -----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]
