(Not sure if it's clear from how I said it when I said "In theory it sounds like a good idea,
and that's what I did before I started using maven ..." but what I meant was "In theory
it sounds like a good idea having the environment specific configuration stuff outside the war file
...")
I think one reason I prefer having everything in the war file is because so far
I've whenever I've need to tweak the configuration and I've also needed to
tweak the code.
Another is because I've only used tomcat, where you're more likely to directly
manage your own configuration stuff.
Thanks for your feedback; it's been good food for thought.
Geoffrey Wiseman wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
