[ 
https://issues.apache.org/jira/browse/FELIX-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

J.W. Janssen updated FELIX-3329:
--------------------------------
    Component/s: Deployment Admin

> 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
>          Components: Deployment Admin
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>         Attachments: FELIX-3329_ResourceDeleteNPE.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to