[
https://issues.apache.org/jira/browse/KARAF-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253230#comment-13253230
]
Christian Schneider commented on KARAF-1360:
--------------------------------------------
I was able to fix the problem by downgrading felix fileinstall to 3.1.10 in
Karaf 2.2.7-SNAPSHOT. So it seems the problem is in fileinstall or the
combination of felix fileinstall and felix config admin. On the other hand it
shows that felix already handles the writing of config files. So I will try to
remove the Karaf code that also does this.
> Configration update doesn't work
> --------------------------------
>
> Key: KARAF-1360
> URL: https://issues.apache.org/jira/browse/KARAF-1360
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 2.2.6
> Reporter: Alexander Osadchiy
> Assignee: Christian Schneider
> Fix For: 2.2.7, 2.3.0, 3.0.0
>
> Attachments: test.zip
>
>
> Configuration update doesn't store changes to the persistent storage.
> See attached example.
> To run example build it with:
> mvn install
> Then put generated bundle "config-update-1.0.jar" to the deploy folder.
> Expected: property "size" value was changed from "500" to "1000" in
> etc/org.apache.karaf.log.cfg
> Actual: changes are not stored to file, but we can see them in Karaf with
> "config:list".
--
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
