[
https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944279#comment-15944279
]
David Jencks commented on FELIX-5549:
-------------------------------------
I suppose for R7 components the specified behavior could be changed so that the
ComponentFactory service is unregistered and reregistered on configuration
change if the component has no modified method. If you think this is a good
idea you should take it up with the EG soon. I hadn't considered this but it
seems plausible.
I don't think this will make factory components significantly more usable, as
there is still no notification to clients relying on the ComponentInstance
rather than a service when one becomes permanently deactivated due to
references becoming unsatisfied in the case that the target filter or minimum
cardinality is specified in either the CA or newInstance configuration.
If what I suggested as a possible bug is indeed a bug, it would reduce the
likelihood of the ComponentFactory service being affected in any way by
configuration changes, which doesn't seem to line up with your desires in any
way.
I continue to think that your needs would be best satisfied by using the felix
extension @DSExt.PersistentFactoryComponent and accessing the components as
services. Have you tried it?
> 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
> Assignee: David Jencks
>
> 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)