I'm going to be doing some prototyping of the jmx support in Spring (version 1.2.1 at this point), with an existing somewhat large Spring application.
The two things I want to show are:
* the ability to dynamically set properties of existing beans
* the ability to "reload" beans that reference properties that have changed
I think the former will be somewhat straightforward, but I'm wondering about the latter. If my Spring properties files (not the XML files) are stored outside of the ear, and I change some values, is there any way to cause the application context to be "reloaded" to reflect the new values, so that beans referencing those properties will get changed property values?
The two things I want to show are:
* the ability to dynamically set properties of existing beans
* the ability to "reload" beans that reference properties that have changed
I think the former will be somewhat straightforward, but I'm wondering about the latter. If my Spring properties files (not the XML files) are stored outside of the ear, and I change some values, is there any way to cause the application context to be "reloaded" to reflect the new values, so that beans referencing those properties will get changed property values?
Comment