-
I created support for generation of config dump file. This file will contain current configuration for any defined bean (active and inactive) including every possible setting and default values.
However it is possible that it will not contain settings of bean which are subbeans of disabled bean as they may not be registered due to fact that parent bean is disabled or inactive.
-
I've checked:
componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4451/ce6dcd8f (2016-09-19/12:32:47), Class=tigase.server.XMPPServer}
But:
-
I couldn't locate the file (I've checked
etc/
and also searched fro ~dump
orproperties
without much luck); -
there wasn't any information in the logs (logs/tigase-config.log@) about the file.
Andrzej Wójcik wrote:
I created support for generation of config dump file. This file will contain current configuration for any defined bean (active and inactive) including every possible setting and default values.
Just to make sure - it will contain the final configuration (i.e. defaults and then settings applied from init.properties, which may have overridden the defaults)?
However it is possible that it will not contain settings of bean which are subbeans of disabled bean as they may not be registered due to fact that parent bean is disabled or inactive.
If I understand correctly this is exactly how it works currently - only enabled components are included in this file.
-
Type |
New Feature
|
Priority |
Normal
|
Assignee | |
RedmineID |
4547
|
Version |
tigase-server-8.0.0
|
Spent time |
0
|
Currently, after complete startup we are saving all available settings/properties in @etc/config-dump.properties@, which is highly useful when one wants to:
investigate final configuration (with defaults applied);
change properties and want to know what is the list of possible options (without going through the documentation).