Thank you Gil, that will come in handy.
Long term I would like to see configuration overhaul.
IMO and following good practices:
Each "component/service" should use POJO's - simple properties
(strings, longs, booleans, list and maps of those)
"Components/services" will not read the configuration, it will be handed
to them.
Configuration loading should be done in the main entry point in OFBiz
and this could take into account multiple sources like:
* files and/or a directory of configs - like conf.d patter in linux /etc
* env properties
* cli args
Config is loaded in one place, components are create with this
configuration passed as Java objects / values.
I think there are a few no-dependencies libraries out there that fit
these requirements.
p.s. I will do some more work on chart in the next months and get back.
Regards,
Eugen
On 02.07.2021 11:11, Gil Portenseigne wrote:
Hello Eugen, and thanks Pierre for the reminder :)
I just wanted to mention there was a previous effort to implement
environment variable configuration [1]. This has not yet be pushed into
trunk, but is used by our customer projects.
You could check the patch and test if it helps you ease the
configuration process.
Regards,
Gil
[1] https://issues.apache.org/jira/browse/OFBIZ-9498
--
Eugen Stan
+40720 898 747 / netdava.com
