Hi,
see comments below.
> 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.
>
Full ACK.
> 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:
>
Yep.
> <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.
Without trying it, the syntax looks ok. (Did use the spring-dm stuff before)
Is your property file "manageable"? The pid with an extra suffix, e.g.
this.is.my.pid-withSuffixForInstances.cfg
You can still go ahead and read the documentation for spring-dm and
transfer it to the
blueprint. There is not much of a difference there, but has some better
examples :)
> First, how is the functionality I've described supposed to be provided by
> the above code?
Since you use the container-managed approach this should be it, make
sure that you only have properties without dots
(. like in this.is.my.special.property) this one won't be injected.
> Second, is there a better way to do this?
No
> Third, happy holidays!
>
Thanx, same to you :)
Achim
> v/r,
>
> Karafman
