The StatementPreparerImpl class is using a rather expensive (performance wise) implementation of getJdbcService(), which seems to be invoked regularly now in each StatementPreparationTemplate#prepareStatement.

The existing getJdbcService() seems was previously used only in exceptional cases, but this newly introduced usage is quite hot. The getJdbcService() method should be optimised so to not become a bottleneck as it's used more often: inject the service in the constructor? Or is there a cheaper way to retrieve it from other things we have here?