-
I adjusted some components and checked change, ie: SessionManager (including every processor), VHostManager, AmpComponent, ClientConnectionManager, S2SConnectionManager.
Clustered versions are also adjusted, however not tested yet.
Still need to work on StatisticsCollector, MonitorComponent, EventBusComponent, etc..
-
I prepared new bootstraping mechanism and mechanism responsible for loading old configuration and trying to convert it into new DSL based format (saves converted config into new file)
New file format looks like this:
--tls-enabled-protocols = 'SSLv2Hello,SSLv3,TLSv1' --debug = 'server,xmpp.impl' --new-connections-throttling = '5290:1100' --cluster-mode = 'true' config-type = '--gen-config-def' beans = '+message-archive' --virt-hosts = 'zeus,test' dataSource { repo-uri = 'jdbc:postgresql://127.0.0.1/tigase?user=test&password=test&autoCreateUser=true' } sess-man { beans = ['message-archive-xep-0136'] message-archive-xep-0136 { class = 'tigase.archive.MessageArchivePlugin' } } c2s { beans = 'urn:xmpp:sm:3' } message-archive { class = 'tigase.archive.MessageArchiveComponent' }
Type |
Task
|
Priority |
Normal
|
Assignee | |
RedmineID |
4001
|
Spent time |
0
|
Issue Votes (0)
Watchers (0)
In version 7.2 we expect to use Tigase Kernel. To be able to use it in as base of Tigase XMPP Server we need to be able to bootstrap kernel with default configuration and apply configuration from properties file. For that we need new class
bootstrap
class which will be responsible for this initialization process.