[
https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868766#comment-15868766
]
David Jencks commented on FELIX-5549:
-------------------------------------
I'm not quite sure what you expect to happen. I'm guessing it might be that
you expect Booter.bindFactory to be called after you update the configuration
with some properties? Is the unbindFactory method called?
I don't see anything in the spec indicating that a configuration change should
affect a ComponentFactory service other than affecting properties of a
component created by calling newInstance. I don't quite recall what happens to
existing instances and don't see a description in the spec, but I think that if
there is no modified method all the existing instances will be destroyed.
Personally I've never found a use for factory components, although I've
suggested that they could be useful if the components created by newInstance
had a lifecycle the same as normal components.
> Factory component fails to reactivate after config changes
> ----------------------------------------------------------
>
> Key: FELIX-5549
> URL: https://issues.apache.org/jira/browse/FELIX-5549
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Environment: Karaf 4.0.8
> Reporter: Alex Soto
>
> A factory component fails to reactive after the configuration changes.
> Initially, the component initializes normally. After it is in Active state,
> the configuration referenced by the component _configurationPid_ changes,
> which causes the component to not activate again.
> A minimal application demonstrating this behavior is available here:
> https://github.com/lexsoto/blueprint-ds-config-reload
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
