Thanks for the reply archetype. You are partly right about our environment, however it's a bit more complex that that; its the beans themselves that may or may not be deployed in certain environments, not just their properties. On app startup, Spring reads my additional context XML file and loads my bean(s) up using
That mechanism works well for us. However we want to keep the configuration to a minimum, and make it as simple as possible for the people who are installing it by reducing the number of properties that need to be set.
It's pretty lean as it is to be honest, but if it's possible to make it even more so I would like to do do it.
Using property placeholders is something I might do (I usually do) but my question is more to do with what configuration options are possible for the LdapContextSource.