[
https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934995#comment-15934995
]
Alex Soto commented on FELIX-5549:
----------------------------------
I am not sure, I was reading again the OSGi spec. Section 112.5.5 of the "The
OSGi Alliance, OSGi Enterprise, Release 6 July 2015" says:
bq. Once any of the listed conditions are no longer true, the component factory
becomes unsatisfied and the Component Factory service must be unregistered. Any
component configurations activated via the component factory are unaffected by
the unregistration of the Component Factory service, but may themselves become
unsatisfied for the same reason.
I think this is not happening (or not consistently happening) when a
configuration change occurs. I am not expert in the spec, so maybe I am
misreading it. I am working on a better sample app illustrating this.
> 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)
