We use a couple ConfigAdmin/FileInstall to load/store the config.
Christian saw that ConfigAdmin itself can implement a persistence manager.
To be honest, I don't see the interest right now as our current solution
works fine.
AFAIR, Christian didn't see any problem around ConfigAdmin, he just want
to use the persistence manager of ConfigAdmin.
Regards
JB
On 09/15/2012 02:06 PM, Guillaume Nodet wrote:
FileInstall does thé persistance, you're right, I forgot about that. But
only for updates on configurations that were loaded by FileInstall in the
first place, so it won't persist new configs.
Christian, what's the exact behavior you see ?
On Thursday, September 13, 2012, Christian Schneider wrote:
Am 13.09.2012 12:14, schrieb Ioannis Canellos:
Christian, since it used to persist things by default, let's just fix the
bug.
I am not sure if it would be a good idea to persist any config pid to
etc. Imagine you have a config admin impl that persists to a DB or a
central server internally.
In this case you would rather not want to persist to the etc dir too.
Apart from that .. How would you fix it? The felix config admin service
does the persistence to etc files internally now.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
