-
I created new
config-mode=setupas described in task description. Here is how empty/defaultetc/init.propertiesfile should look like:'config-type' = 'setup' http () { setup () { 'admin-user' = 'admin' 'admin-password' = 'tigase' } }For Tigase XMPP Server starup (normal)
config-modeshould be:-
not set (no entry for this key)
-
default -
--gen-config-def
-
-
I've restored this old config types which got lost during conversion of Tigase XMPP Server to kernel based architecture.
So we have following config types:
default- it replaces old config types--gen-config-def@, @--gen-config-alland--gen-config-default
In this case we load default beans we assume that should be loaded.
-
session-manager- replaces--gen-config-sm -
connection-managers- replaces--gen-config-cs -
component- replaces--gen-config-comp -
setup- new type of config created for initial configuration of Tigase XMPP Server
I made sure that each config type loads similar components as it did in previous versions.
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
4880
|
As suggested in https://projects.tigase.org/issues/4876#note-5 we should include new config guide
config-type=setupwhich would result in different defaults being used - bare-bone Tigase simply launchinghttp-apicomponent withsetupmodule - it should mitigate compatibility issue and lack of initial config during startup (something like--gen-config-compwhich only load components related for external component configuration)