|
From: <spr...@wr...> - 2008-02-01 17:39:43
|
Hi Bryant, a colleague of mine has programmed a = "ReloadingPropertyPlaceholderConfigurer" have a look at: = http://www.wuenschenswert.net/wunschdenken/archives/127 . =20 Regards, Jan=20 =20 =20 -- Jan Tietjens Software Engineer CoreMedia Ludwig-Erhard-Str. 18 20459 Hamburg, Germany <www.coremedia.com> CoreMedia AG Executive Board: S=F6ren Stamer (CEO), Dr. Klemens Kleiminger (CFO) Supervisory Board: Prof. Dr. Joachim Schmidt (Chairman) Trade Register: Amtsgericht Hamburg, HR B 76277 =20 From: Bryant Harris - bry...@ho... = [mailto:+spring-dev-list+tietjens+cec8b94c39.bryant_harris#hotmail.com@sp= amgourmet.com]=20 Sent: Freitag, 1. Februar 2008 01:01 To: spr...@li... Subject: [Springframework-developer] Hot updating of bean properties = =20 I had an idea and wanted to see if anyone has persued it. =20 So you know how the ProperyPlaceholderConfigurer allows you to = externalize properties using ant style notation ${some.prop} in bean = definitions? =20 What if you could change those values at runtime and have the Configurer = hot update the property on the bean with the latest value? =20 Obviously the configurer would need to keep track of the beans created = from the bean definitions it first updates, but I don't think this is = something that would be too hard to do. =20 Also, I realize that not all beans are amenable to having their = properties updated. So although a boolean attribute might be easily = switched, updating say the URL on a JDBC connection would be more = complicated since it might imply that all connections should be flushed, = something the standard datasource might not do (or maybe it throws an = IllegalStateException). =20 At anyrate, has anyone tinkered around with an idea like this? =20 Thanks, =20 Bryant |