Hi,
I created a Karaf feature that contains a configuration block and when I
install it into Karaf it is properly recognized and registered with the
given PID. I can however not find where Karaf stores that configuration
information. I assumed that a new file with the corresponding PID will be
cre
Hi Lothar
it's in memory by default.
tag in feature only populate ConfigAdmin (memory only by
default), and doesn't flush in the etc folder.
To populate the etc folder, use : it populates the etc
folder and load ConfigAdmin using this config file.
Regards
JB
On 06/24/2013 03:30 PM, Lotha
Hi,
JB told you only half the truth (21) ;)
Configuration Admin service keeps the configuration in Memory that's
correct but it's also stored in the cache folder where the bundle
information is stored.
The etc folder is actually used by the File Installer that scans for
changes and populates the
Thanks Achim, you are right, I forgot to mention the cache folder ;)
Another thing: etc folder is used by FileInstall for load of the
configuration, but also by config:update command and config MBeans to
flush a configuration in the etc folder (for instance config:edit &&
config:update creates
Hi JB,
I think we have a issue for that, and it should be an optional feature :)
https://issues.apache.org/jira/browse/KARAF-545
regards, Achim
2013/6/24 Jean-Baptiste Onofré
> Thanks Achim, you are right, I forgot to mention the cache folder ;)
>
> Another thing: etc folder is used by FileIns
Correct, and it's a pita that I forgot it: I created this Jira ;)
Regards
JB
On 06/24/2013 03:50 PM, Achim Nierbeck wrote:
Hi JB,
I think we have a issue for that, and it should be an optional feature :)
https://issues.apache.org/jira/browse/KARAF-545
regards, Achim
2013/6/24 Jean-Baptiste O
I think it should at least create the file when the data is modified via
config amin (e.g. the web interface). Creating it on feature install is a
bonus, but not strictly necessary
Lothar Werzinger
Sent from a mobile device.
--
This message and any attachment (the "message") is intended solel
Through the web-interface should already be, if I remember correctly.
There used to be a special flag or property available in the webconsole for
this.
regards, Achim
2013/6/24 Lothar Werzinger
> I think it should at least create the file when the data is modified via
> config amin (e.g. the w
Currently config admin keeps track if the config was originally read
from a file. If yes then changes are also written back to the original file.
If no then changes are only done in memory.
So I think it would make sense to have an option on the config element
to decide if it should be persiste
It does that if the FileInstall felix.fileinstall.filename property
exist in the configuration PID.
For the config element, we can do exactly as we do in config:update
command and Config MBean.
Regards
JB
On 06/25/2013 08:52 AM, Christian Schneider wrote:
Currently config admin keeps track
ahh, yes that's the property one needs ... (and I was looking for ...)
so basically it should already do if one supplies this property in the
config element,
wouldn't it?
So basically we should close that issue with a little bit of documentation
:-)
If this property
felix.fileinstall.filename=foo.
Yup, exactly ;)
Regards
JB
On 06/25/2013 10:17 AM, Achim Nierbeck wrote:
ahh, yes that's the property one needs ... (and I was looking for ...)
so basically it should already do if one supplies this property in the
config element,
wouldn't it?
So basically we should close that issue with a litt
Just tested it,
unfortunately it's not enough to have this property set when installing
this via features.
Therefore we still need to program something, the issue needs to stay open.
regards, Achim
2013/6/25 Jean-Baptiste Onofré
> Yup, exactly ;)
>
> Regards
> JB
>
>
> On 06/25/2013 10:17 AM,
Anyway, it would have been just a workaround: element should
behaves as config:update or ConfigMBean.
Regards
JB
On 06/25/2013 11:34 AM, Achim Nierbeck wrote:
Just tested it,
unfortunately it's not enough to have this property set when installing
this via features.
Therefore we still need to
Hi
How can I force to create the config file in etc using
config:edit/config:update with nonexisting pid in 3.0.0? I tried to add
the felix.fileinstall.filename property but the file is not created.
Best regards
Krzysztof
On 25.06.2013 10:17, Achim Nierbeck wrote:
ahh, yes that's the proper
Hi Krzysztof,
config:edit should do the trick straight forward using the ConfigAdmin
persistence. However, I don't see the persistence adapter call (I
remember that Christian did a change around that).
I gonna create a Jira about that and fix that for 3.0.1.
Regards
JB
On 12/26/2013 03:15 A
16 matches
Mail list logo