Ok, thanks.
I still don't see what the problem is with having all of the configuration in
the war file.
In theory it sounds like a good idea, and that's what I did before I started
using maven, but with maven and its profiles it's too easy to simply make 3
wars for each dev, qa, and prod environment. Having environment specific stuff
outside of the war, and it would seem to me, not controlled by the pom, seems
like extra, and possibly error prone work.
Geoffrey Wiseman wrote:
On Sat, Nov 8, 2008 at 1:01 PM, Rusty Wright <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
But I do have multiple environments.
How do you manage the different configuration files for the
different environments?
Do they have different names and the application figures out which
environment it's on and then uses the appropriately named
configuration file? I tried that; it's too fragile.
Or do the configuration files have the same name on all environments
and you have to ensure that the right ones are installed? That's
what I'm using now with symbolic links. For example, db.properties
is what the app uses but it's a symbolic link to db-dev.properties.
I mostly to the latter -- i've experimented with some kind of
centralized configuration with discovery, but haven't ended up with
something i'm happy with, so I mostly just load configuration from the
classpath with a predefined name, and use the container to add the
appropriate directory into the classpath in each environment.
--
Geoffrey Wiseman
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
