Common strategies when defining Spring beans for different environments

Question

What are common strategies for defining a bunch of beans, which are used differently in development and production environments?

Let\'s say I have 2 beans, each impl

Answer 1

This is what I have been using in many of my projects. Have all your environment independent beans in say common.xml and all others in say dev.xml/qa.xml/prod.xml. If you are using ant to build your project,then supply the environment as an argument to the build process and let the build script include appropriate env.xml and omit others. I mean,the build script will copy dev.xml as env.xml if its a dev environment or qa.xml as env.xml if its QA. So the code which loads the bean definitions will always use "common.xml,env.xml".