One thing i've recently added to blueprint is a cm:reload flag that reload the whole blueprint application when the configuration changes. I found that was an easy and efficient way. But it's not release yet and only available in trunk.
Le vendredi 17 décembre 2010, Mike Van <[email protected]> a écrit : > > I have a database bean and I'm using ConfigAdmin to allow me to make changes > to an .cfg file, and have those properties set in karaf. This is working. > Woot!!! > > I've noticed that individual bundles need to be restarted in order to use > these new properties. While karaf only takes six thousandths of a second to > do this, its still an extra step my users will need to perform, and... well > we know that the weakest link in an application is the end-user so... nuff > said. > > What I'd like to happen is when a property is changed in the .cfg file, and > that property is picked up and set in ConfigAdmin, to have every bundle > using that property to also update. I thought that using a managed service > would do this: > > <bean id="configTest" class="com.test.ConfigTest"> > <osgix:managed-properties persistent-id="myPropertyFile" > update-strategy="container-managed" /> > <property name="propertyValue" value="${propertyValue}"></property> > </bean> > > However, it doesn't. > > First, how is the functionality I've described supposed to be provided by > the above code? > > Second, is there a better way to do this? > > Third, happy holidays! > > v/r, > > Karafman > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Managed-Properties-question-tp2107407p2107407.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
