> You can implement your own PersistenceManager (ConfigAdmin service).
OK, I'm actually super confused now (not hard).
felix configadmin appears to have logic in it that persists configurations to
and from files. It's unclear in the karaf environment where the
FilePersistenceManager is
You could also look at the read-only implementation of ConfigAdmin we have
in Karaf.
That can easily be used to remove fileinstall completely, as done in the
static configurations.
https://github.com/apache/karaf/tree/master/services/staticcm/src/main/java/org/apache/karaf/services/staticcm
Hi Tom,
You can implement your own PersistenceManager (ConfigAdmin service).
Regards
JB
On 10/06/2017 01:07 PM, t...@quarendon.net wrote:
I can see KARAF-418, but that's pretty old, and sounds like it was considered
unnecessary? Is there anything else I can't find?
I don't necessarily want
I can see KARAF-418, but that's pretty old, and sounds like it was considered
unnecessary? Is there anything else I can't find?
I don't necessarily want to store things in a database, I just want different
behaviour to normal, to provide my own implementation of something that listens
to
Hi
I guess you want to use an alternative backend to the filesystem (a database
for instance).
In that case we have a Jira about that and you can provide your own persistence
backend.
Regards
JB
On Oct 6, 2017, 12:30, at 12:30, t...@quarendon.net wrote:
>I'm trying to establish some
I'm trying to establish some alternative configuration behaviour than what
felix-fileinstall gives me.
I have written a very simple component that reads configuration files in from
/etc and updates config admin with the information, much like fileinstall does.
I can run this and it appears to
