I've been writing some tests to verify what happens when you update component 
configurations (from ca) that specify reference targets and I'm unsure what 
should happen for factory components.

It seems pretty clear from the spec that you can have a factory component with 
configuration-policy="require" and that at least the initial configuration 
properties for the factory come from config admin + xml defaults and these 
properties get combined with the ones you specify in factory.newInstance(props).

So what happens when you update the config in ca?

Right now just the factory gets configuration props updated, but all existing 
components are unmodified.

I think this is wrong and all the existing components should also have the 
config update applied.

Is there any language in the spec I missed?  Any opinions or comments?

112.5.5 ends with this:

Once a component configuration created by the Component Factory has been 
deactivated, that com- ponent configuration will not be reactivated or used 
again.

which might suggest that static references won't work with this kind of update 
or that what I think should happen is wrong.  But this seems kinda silly if the 
component is registered as a service. 


many thanks
david jencks

Reply via email to