Allow the autoconf resource processor to defer the setting of the configuration
until ConfigurationAdmin is available
---------------------------------------------------------------------------------------------------------------------
Key: FELIX-3329
URL: https://issues.apache.org/jira/browse/FELIX-3329
Project: Felix
Issue Type: Task
Reporter: Marcel Offermans
Right now, autoconf will always fail if you start out with an empty container
and install a deployment package with all your bundles, including configuration
data and ConfigurationAdmin, because at the time it tries to find the
ConfigurationAdmin service, that won't be started yet. A solution would be to
(in that case) defer setting the configuration until the service becomes
available. The downside of this is that we never know for sure if this will
work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira