|
Andrzej Wójcik (Tigase) opened 9 years ago
|
|
Just a small comment - I think it would make sense to allow configuration on per-component-class in addition to per-instance (like now, where all configuration is based solely on component name, i.e.: @muc/…@) |
|
|
I think this may be considered as done. Original implementation done in this task was removed as it used older version of groovy and caused compilation issues. New version of DSL configuration reader was implemented in task #4001 during implementation of bootstrap. |
| Type |
Task
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
2876
|
| Spent time |
90h
|
Issue Votes (0)
Watchers (0)
In near future Tigase Kernel should take over responsibility to create and configure component instances.
We need a way to configure kernel and component instance - pass properties set by user in configuration file and so on.
As
init.propertiesfile is plain properties file it is difficult to define structured configuration. It would be better to have configuration in form of Groovy-DSL file in which property values would have proper types and it would be easy to pass this configuation directly to Tigase Kernel for configuration of server component.