[
https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936668#comment-15936668
]
David Jencks commented on FELIX-5549:
-------------------------------------
Are you changing what you are complaining about? I don't think your example
had ConfigurationPolicy.REQUIRE. Are you now suggesting that the spec would
be clearer if it included a third condition, something like....
If the configurationPolicy is REQUIRE then there are configurations for each of
the components pids.
I think there may be a different bug, which I suspect is a mistake in the
spec. The second condition specifies using the component properties from the
component description, i.e. the xml before merging with any configurations,
whereas the implementation IIRC uses the properties from merging the xml with
configurations. I suspect this is an historical error from not updating the
part of the spec dealing with factory components when configuration from config
admin was introduced.
> 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)
