karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-1189) Feature installation: synchronization between copiing configuration files and installing/starting bundles
Date Wed, 28 Mar 2012 09:54:27 GMT

    [ https://issues.apache.org/jira/browse/KARAF-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240328#comment-13240328

Christian Schneider commented on KARAF-1189:

I think the other issue is not about the same problem. Spring DM has no measure to wait for
configs or update on changes.
If you deploy a config using a file then you will always have the uncertainity when it is
updated in config admin.

So I see three possible solutions: 
- Update the config using the jmx bean or command. In that case my fix for the other issue
guarantees that the data is there when you install your bundle after this.
- Use the ManagedService directly so you can pull up the service not at bundle start but rather
when the config is there. This probably does not work well with defining the service in spring.
- Use blueprint which supports config updates and not starting when there is no config
About the issue in Karaf: I donĀ“t think we can really fix this in karaf as the problem is
with spring dm.
 So if you agree I close this issue.
> Feature installation: synchronization between copiing configuration files and installing/starting
> ---------------------------------------------------------------------------------------------------------
>                 Key: KARAF-1189
>                 URL: https://issues.apache.org/jira/browse/KARAF-1189
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-core
>            Reporter: Andrei Shakirin
>            Assignee: Christian Schneider
>              Labels: configuration, features,
> Hi,
> Actually there is no synchronization between installation/starting bundles and copiing
configuration files.
> It causes sometimes that bundles with OSGi services are already started, but appropriate
configuration is not yet accepted by ConfigurationAdmin. Result is failed services by first
installation. After restart problem is resolved.
> Question: is it basically possible to wait untile configuration files are accepted by
ConfigurationAdmin and only after it start bundles from the feature?
> Regards,
> Andrei.

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


View raw message