[
https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936274#comment-15936274
]
Alex Soto edited comment on FELIX-5549 at 3/22/17 1:18 PM:
-----------------------------------------------------------
I am sorry I missed the part about the conditions, and there, I think, lies the
problem. For me, the configuration _should_ be one of the conditions, same as
the references. For example, if I annotate the Worker component with
"configurationPolicy = ConfigurationPolicy.REQUIRE", then the Component Factory
service is not registered _until_ a configuration is created. Why is this? This
behavior makes that the existence of the configuration a necessary condition,
perhaps not explicitly listed as such, but in practice it behaves like one. If
the existence of the configuration is not one of the conditions, then the
Component Factory service should have been registered immediately, but this
would not make much sense, since creating instances would result in error.
was (Author: alex.soto):
I am sorry I missed the part about the conditions, and there, I think, lies the
problem. For me, the configuration _should_ be one of the conditions, same as
the references. For example, if I annotate the Worker component with
"configurationPolicy = ConfigurationPolicy.REQUIRE", then the Component Factory
service is not registered _until_ a configuration is created. Why is this? This
behavior makes that the existence of the configuration a necessary condition,
perhaps not explicitly listed as such, but in practice it behaves like one.
> 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)
