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? > > 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? > > 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. Programs should not muck with their own configurations on their own initiative. Sysadmin.s expect the settings they make to stay set. If they need to override default values within a .war, their changes shouldn't be blown away with every redeployment. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
pgpbdOea3tLOE.pgp
Description: PGP signature
