Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Tue, 14 Jan 2014 07:46:58 +0000 (UTC)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12686390.1388042754354.92399.1389685618553@arcas>
In-Reply-To: <JIRA.12686390.1388042754354@arcas>
References: <JIRA.12686390.1388042754354@arcas>
Subject: [jira] [Commented] (KARAF-2656) Config service doesn't create a
 file in etc if it doesn't exist
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-2656?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1387=
0489#comment-13870489 ]=20

Christian Schneider commented on KARAF-2656:
--------------------------------------------

Ok . Just wanted to say that from a user perspective I think I could wait f=
or the fix in config admin and live with the workaround till then.

> Config service doesn't create a file in etc if it doesn't exist
> ---------------------------------------------------------------
>
>                 Key: KARAF-2656
>                 URL: https://issues.apache.org/jira/browse/KARAF-2656
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-config
>    Affects Versions: 3.0.0
>            Reporter: Jean-Baptiste Onofr=C3=A9
>            Assignee: Jean-Baptiste Onofr=C3=A9
>            Priority: Blocker
>             Fix For: 2.4.0, 3.0.1
>
>
> The config service doesn't create a file in etc if the file already exist=
s.
> Previously (in Karaf 2.x) we explicitely created the config file. Now we =
delegate to ConfigAdmin persistence, but we don't provide any persistence a=
dapter.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)