[
https://issues.apache.org/jira/browse/FELIX-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-4698.
-------------------------------------
Resolution: Won't Fix
Closing old issue, if it's still an issue with latest SCR implementation please
reopen with updated information
> SynchronousConfigurationListener
> --------------------------------
>
> Key: FELIX-4698
> URL: https://issues.apache.org/jira/browse/FELIX-4698
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.8.2
> Reporter: Jens Offenbach
> Labels: configuration, configurationadmin, scr
>
> When you directly create/update a configuration and delete it right after
> creation, the component instance creation of components which preconditions
> become fulfilled (using ConfigurationPolicy.REQUIRE) often fails. The reason
> is that events from the ConfigurationAdmin are delivered to SCR
> asynchronously. This results in the following behavior: SCR receives a
> configuration update event and accesses e.g. its properties. The call fails
> because the configuration was deleted in the meantime. A solution would be to
> implement SynchronousConfigurationListener in the class CongurationSupport
> instead of ConfigurationListener. That forces the ConfigurationAdmin to
> deliver the update events before someone can delete the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
