L3 - Default Context:
The current state of the import mediator setup is quite complex. They are instantiated by a mix of injection across class hierarchy and prototype bean arguments passed to the spring beanFactory + an init method that initializes other fields calling the beanFactory.
This has several downsides:
- it's not easy to grasp all the dependencies while working on them (it's a collection of properties across the class hierarchy due the to complex setup
- strict dependency on spring beanFactory
- they are not easy to unit-test -> dependency on spring and a lot of manual mocking by internal property access required
AT:
- clean up the class hierarchy to use ctor parameters over injection
- extract setup code from init methods into dedicated factoryClasses/Beans
- consider writing unit tests to verify the behavior of major mediator classes present(timestampBased, all entities, scrollBased)
test backoff logic implemented in `BackoffMediator`
This is the controller panel for Smart Panels app
- mentioned in
-
Page Loading...
1.
|
Refactor Import Mediators |
|
Done | Unassigned |
2.
|
Refactor Import Services |
|
Done | Unassigned |
3.
|
Add unit tests for import backoff logic |
|
Done | Unassigned |