Hi All,

        This seems like it'd be easy but I'm just not connecting the dots here. 
I've created a component with configurationFactory set to true. I see then that 
I can create multiple instances of these within Felix, and my code for this 
component nicely lists all of the configurations made against it. All is well. 
The next step is having a separate service read all of these configurations 
that were created. 

        So my approach has been to simply have a reference to this component in 
my service. My problem is that changes to the configuration component aren't 
propagated to the depending service. I thought setting a reference policy of 
dynamic would do it, but I still seem to hold onto the original values after 
re-configuring.

        So I'm looking for ideas on what is probably a very simple concept. How 
do I reference a separate component's configurations and receive changes from 
them? Do I need to implement eventing to receive these updates or is there a 
better way to establish the reference so that this works?

Thanks in advance

Mike Ottinger
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to