You could either read this property from the database and make use of the @Cacheable and perhaps some sort of ehcache time to live setting to re-read the properties when they are accessed after that time is exceeded. Or you could use the re-loadable properties. However there is not a good way to do it with the property source configurer.
Here is a solution someone came up with using
java 7 features
http://www.morgan-design.com/2012/08/reloadable-application-properties-with.html
There are some other work arounds you can find by googling around. You could also see if you could make things work with
http://static.springsource.org/spring/docs/3.2.x/javadoc-api/org/springframework/context/support/ReloadableResourceBundleMessageSource.html
Remember with the newer PropertySourceConfigurer you get your properties registered in the environment. This means you can do
If you took an approach of registering your changed properties with the Spring environment you would not need to worry about changing bean injections, as it looks it up from the environment.