-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark,
Mark H. Wood wrote: > On Wed, Sep 12, 2007 at 09:38:45AM -0400, Christopher Schultz wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Balázs, >> >> [EMAIL PROTECTED] wrote: >>> 4. Using Tomcat Administrator application the admin changes >>> environment settings defined in >>> conf/Catalina/localhost/warname.xml (which was extracted from the >>> war). >> Why would you make an administrator do this when you can make it >> part of the deployment process? > > Why would you make the deployment process so hostile when you could > let the administrator control his own machine? According to the OP, the administrator doesn't want to do his job. IF it's got to be done, and the admin won't do it, then someone else has to. >>> The only way was to put resource links to the >>> war/META-INF/context.xml that link to GlobalResources. >> This isn't true. You can put "real" resources into >> META-INF/context.xml. Why not just do that? > > Perhaps because one is deploying on several different hosts and each > needs different settings? I think you're missing the point: I'm suggesting that he automatically configure whatever he needs on the fly. >>> But now I have to deploy the same unmodified war many times to >>> the same tomcat so I have to use different settings at each >>> webapp. >> >> I would highly recommend changing your deployment strategy so that >> you are deploying a /modified/ copy of your WAR file each time -- >> one that has the correct settings for your environment. > > Ewww. > > I've seen this come up several times (and brought it up myself), and > everyone is dancing around the real issue: Tomcat seriously violates > the Principle of Least Surprise. So, you think it's surprising that when you have to work around the standard deployment procedure (use of META-INF/context.xml) it becomes a real PITA? That's not surprising to me at all.. an exception case is an exception case. > Programs should not muck with their own configurations on their own > initiative. Sysadmins expect the settings they make to stay set. These settings /do/ stay set, unless you re-deploy the application, at which point the old deployment information is stale and ought to be refreshed. > If they need to override default values within a .war, their changes > shouldn't be blown away with every redeployment. Except that anyone who /wants/ this behavior would have the opposite complaint. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG6ADR9CaO5/Lv0PARAsNTAKCyh5coUNXKNTX7TgLChYsCBOmhKACeMzm+ 58pT4H9emPzFHHbSChaxE94= =tvUt -----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]
