You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2009/10/19 19:49:59 UTC

[jira] Updated: (FELIX-1718) karaf shell config:update command should persist / override configurations from the etc/ folder

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

Guillaume Nodet updated FELIX-1718:
-----------------------------------

    Summary: karaf shell config:update command should persist / override configurations from the etc/ folder  (was: Karaf Shell Config Update command should be able to persist updates across container restarts)

Actually, the configuration is already persisted by config admin but is overriden on restart by the content from the etc/ folder.


> karaf shell config:update command should persist / override configurations from the etc/ folder
> -----------------------------------------------------------------------------------------------
>
>                 Key: FELIX-1718
>                 URL: https://issues.apache.org/jira/browse/FELIX-1718
>             Project: Felix
>          Issue Type: Improvement
>          Components: Karaf
>            Reporter: Sergey Beryozkin
>             Fix For: karaf-1.0.2
>
>
> config:update command results in updates being persisted in memory only; it would be great for updates be retrievable after the container has been restarted
> perhaps ConfigAdmin can be told to save the updates to the original cfg file but may be another option would be to save them to the ConfigAdmin bundle cache so that updates can be reverted

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.