Configuration not provided to components if Configuration Admin is not active
while setting up components
---------------------------------------------------------------------------------------------------------
Key: FELIX-2510
URL: https://issues.apache.org/jira/browse/FELIX-2510
Project: Felix
Issue Type: Bug
Components: Declarative Services (SCR)
Affects Versions: scr-1.4.0
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: scr-1.4.2
In earlier versions of the Declarative Services implementation, configuration
for the components has been provided by the Declarative Services bundle
registering ManagedService[Factory] services for each component registered.
This ensured configuration to be provided by Configuration Admin service to the
components once Configuration Admin service is active, configuration is present
and a Component is here to take it.
The drawback is, that this mechanism operates completely asynchronous
(potentially causing components to be cycled during fire-up). Thus
Configuration is now provided to the Components by the Declarative Services
implementation by asking the Configuration Admin service for configuration on
behalf of the components. Configuration updates are forwarded by the DS
registering a ConfigurationListener.
The problem now is, if Declarative Services is started (and has set up
Components) before the Configuration Admin service is present, configuration
will never be provided to components.
To fix this, Declarative Services should register for service events to hear
when Configuration Admin becomes present to be able to forward any
configuration to the components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
