Jan 25th, 2011, 08:40 AM
best option for dynmically choosing properties file
I have a client that wants us to provide one WAR that can be used through tree different deployment environments, DEV, TEST and PROD. (Basically with as little work for them on the deployment side, the better)
There are a few configuration options that change through these environments (DB credientials, location of SMTP server, etc).
Does anyone have a recco on how I might achieve this in a 'spring' way?
On other development platforms I have used systems that either identify the machine name (.NET) or recognize which URL (domain and port) they are running under to decide which configuration file to load.
I'm just looking for some suggestions on how which direction would make sense in the spring world.