Plugin config mechanism
At the moment DMX has a global config file (config.properties
). We need a per-plugin config mechanism.
It might be realized like this:
- The config files are named like the respective plugin, but without version number, e.g.
dmx-ldap.properties
. - The config files are stored in the same directory as the global config file (as configured by
java.util.logging.config.file
). An alternative approach is storing them together with the respective plugin file (inbundle-deploy
). - When starting a plugin the Core reads its config file (if exists) and makes the therein defined properties available as Java system properties.
- Hot-Config: plugin config changes are active without restarting the platform (as it is required now). The Core re-reads the config when the plugin is restarted, e.g. by
refresh
gogo shell command. Alternatively the platform could scan the config directory periodically and propagate changes automatically (without manual refresh).