Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9B359200C3C for ; Mon, 3 Apr 2017 18:06:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 99BF1160B76; Mon, 3 Apr 2017 16:06:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DE7CC160B8F for ; Mon, 3 Apr 2017 18:06:46 +0200 (CEST) Received: (qmail 61978 invoked by uid 500); 3 Apr 2017 16:06:45 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 61882 invoked by uid 99); 3 Apr 2017 16:06:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2017 16:06:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1FA00CA889 for ; Mon, 3 Apr 2017 16:06:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id y9Jfucw-QiWx for ; Mon, 3 Apr 2017 16:06:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 895275FE48 for ; Mon, 3 Apr 2017 16:06:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BBCBAE0D34 for ; Mon, 3 Apr 2017 16:06:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id D30DF24026 for ; Mon, 3 Apr 2017 16:06:41 +0000 (UTC) Date: Mon, 3 Apr 2017 16:06:41 +0000 (UTC) From: "Guillaume Nodet (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KARAF-4829) Make sure configFile in features makes config available early MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 03 Apr 2017 16:06:47 -0000 [ https://issues.apache.org/jira/browse/KARAF-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953710#comment-15953710 ] Guillaume Nodet commented on KARAF-4829: ---------------------------------------- This is not an issue for simple properties file. The enhanced config files containing typed values are not fully supported and it must be done in multiple locations in Karaf, but also FileInstall. I've raised a JIRA for that, and I started implementing a file to read / write / update those configurations properly. > Make sure configFile in features makes config available early > ------------------------------------------------------------- > > Key: KARAF-4829 > URL: https://issues.apache.org/jira/browse/KARAF-4829 > Project: Karaf > Issue Type: Improvement > Components: karaf-config > Affects Versions: 4.0.7 > Reporter: Christian Schneider > Assignee: Guillaume Nodet > > We currently have the config and configFile elements in feature files. > Config writes the given entries to ConfigAdmin while configFile writes a file. > So configFile is needed if the user should get a nice file to edit. The problem with configFile is that ConfigurationAdmin reads the files asyncronously. So bundles of the feature might already be started at the time the config is written. > So bundles might need to restart or if they only process the config once are in a kind of invalid state that does not relfect the config from the feature. > So I propose to also write the config to ConfigAdmin if configFile is used. This should allow the bundles to come up in the correct state from the start. -- This message was sent by Atlassian JIRA (v6.3.15#6346)