On Mon, Nov 10, 2008 at 7:29 PM, Martin Gainty <[EMAIL PROTECTED]> wrote:
> i agree with randy > > murphy's law applies.. > if <dev/qa/prod> properties was packaged with the war then you would'nt > have to worry about finding it... > its always in the war > Honestly, if that works for you, so be it. I personally don't want to have to rebuild the WAR to reconfigure. I don't want operations people to have to dig around inside a WAR or a source repository. I want them to be able to take the WAR, drop it somewhere, edit a text file and you're done. I want to know that if I build a new version of the WAR, I don't have to worry if they've changed configuration settings since I last gave it to them. I want to know that if there's a new environment, the developers don't need to be involved to get it up and running. These are the kinds of advantages that I feel like i'm getting from externalizing the configuration, but there are other ways to go about it. - Geoffrey -- Geoffrey Wiseman
