I'd contend that once you hit QA it's an admin's job to point to an appropriate DB server for instance, not a dev's (although the devs will clearly have a say)... However, none of this should be built into the EAR and therefore can be changed in any environment without the EAR itself changing.
Frank -----Original Message----- From: Al Sutton <[EMAIL PROTECTED]> Sent: Sunday, June 29, 2008 9:06 AM To: Struts Developers List <dev@struts.apache.org> Subject: Re: [OT] Re: environment awareness (project stage in JSF) Then the questoin becomes "Hows does the developer create a configuration set when the application is released which uses the database server which is chosen by the tech support team when things start going wrong at a later date?" Al. Dave Newton wrote: > --- On Sun, 6/29/08, Al Sutton <[EMAIL PROTECTED]> wrote: > >> If the techies at DR just had a "dev, test, or prod" >> switch how could they have done that? >> > > How could they do it if they had to change code? > > Complex environments require complex configuration management; I'm not sure > how the example contraindicates that. > > Lots of environments (even my non-Orbitz-scale ones) require more > configurability than "dev, test, prod", although they can be useful > shorthands for configuration sets. > > Dave > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
