Hi Jean,
As you highlighted "having all in one config is possible, but it gives less
flexibility in
term of update/reload"
Any idea to implement placeholders like below in feature.xml by this we have
one config file with flexibility and these placeholder get update before
deployment?
Yes, no problem, you can gather all in the same config.
However, all depends how you did the bundles using the config.
If you use ManagedService: it's linked to an unique config.
If you use blueprint or scr, it's like a ManagedService.
If your bundle just use ConfigAdmin when needed, no problem:
I am looking for all in an unique cfg file. So can we change like below?
config
config
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi,
By one file, you mean gather all in an unique cfg file or one feature ?
Having all in one config is possible, but it gives less flexibility in
term of update/reload.
One feature containing all configs is also possible, just use the
feature in other features:
config
i have configuration for components like below, i want to consolidate all
below config in one file, so all feature get config from that file.
how i change below feature file to achieve it?
http://karaf.apache.org/xmlns/features/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
