Refactor ResultHandler type hierachy #336
Milestone
Comments
jvalkeal
added a commit
to jvalkeal/spring-shell
that referenced
this issue
Dec 21, 2021
- Replace main use of ResultHandler with ResultHandlerService which is a framework type of impl for handlers found from conversion service. This handles types better and easier to handle with bean cycles, etc. - Removed IterableResultHandler to think about these use cases later when further refactoring is done. - TypeHierarchyResultHandler is removed and better functionality now via ResultHandlerService. - Relates spring-projects#336
jvalkeal
added a commit
that referenced
this issue
Dec 21, 2021
- Replace main use of ResultHandler with ResultHandlerService which is a framework type of impl for handlers found from conversion service. This handles types better and easier to handle with bean cycles, etc. - Removed IterableResultHandler to think about these use cases later when further refactoring is done. - TypeHierarchyResultHandler is removed and better functionality now via ResultHandlerService. - Relates #336
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On big issue with a result handling is that there is a ResultHandler and then thigns are interconnected in other handlers i.e. having main handler as TypeHierarchyResultHandler, etc.
Come up with new ResultHandlerService which can be designed in a way by taking a lot of concepts from framework ConversionService.
The text was updated successfully, but these errors were encountered: