You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already accept RowMapperFactory in StringBasedJdbcQuery that could serve as abstraction to not require BeanFactory. JdbcQueryLookupStrategy provides a RowMapperFactory implementation so that JdbcQueryLookupStrategy could serve as entry point for a RowMapperFactory implementation using BeanFactory. We can extend RowMapperFactory to resolve bean references and reduce so coupling in StringBasedJdbcQuery.
The text was updated successfully, but these errors were encountered:
We ask BeanFactory to resolve references for ResultSetExtractor and RowMapper. I would like to extend RowMapperFactory to be able to do that so that we move the lookup into an implementation instead of passing BeanFactory around.
Refactor JdbcLookupStrategy to not generally require BeanFactory. Reintroduce deprecated setBeanFactory(…) method.
See #1872
Original pull request: #1874
We already accept
RowMapperFactory
inStringBasedJdbcQuery
that could serve as abstraction to not requireBeanFactory
.JdbcQueryLookupStrategy
provides aRowMapperFactory
implementation so thatJdbcQueryLookupStrategy
could serve as entry point for aRowMapperFactory
implementation usingBeanFactory
. We can extendRowMapperFactory
to resolve bean references and reduce so coupling inStringBasedJdbcQuery
.The text was updated successfully, but these errors were encountered: