[
https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935347#comment-15935347
]
David Jencks commented on FELIX-5549:
-------------------------------------
The conditions referenced in the spec are:
• •
The component is enabled.
Using the component properties specified by the component description, all the
component's
references are satisfied. A reference is satisfied when the reference specifies
optional cardinality or there is at least one target service for the reference
Your Worker component has no references, so the second condition is always
satisfied. You didn't disable the component so the first condition remains
satisfied. Why do you think this should lead to the ComponentFactory service
for Worker to be affected?
As I have pointed out before, since Worker has no modified method, whenever you
change the configuration, all the Worker instances will be permanently
discarded without any notice to the uses getting the instance from the
ComponentInstance rather than through the service registry..
> 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)
