-
I've found that there is a single instance implementing
MonitorComponent
but referenced by multiple delegated bean configs. This was result of old declaration inAbstractKernelBasedComponent
which createddelegated bean config
for component to make sure it is available under namecomponent@. It is pointless as component is almost always available as @service@, so I removed code responsible for creation of duplicated bean config and updated code referencing to component bean as @component
to useservice
instead.
Type |
Bug
|
Priority |
Normal
|
Assignee | |
RedmineID |
5085
|
Version |
tigase-server-8.0.0
|
Spent time |
0
|
Issue Votes (0)
Watchers (0)
When running tests in #4348 with the default config there is a following exception @Too many beans implemented class class tigase.monitor.MonitorComponent@: