This is particularly useful for delegating to existing data access code
that expects a Connection to work on and throws SQLException. For newly
written code, it is strongly recommended to use JdbcTemplate's more specific
operations, for example a query or update variant.
JdbcTemplate#execute(ConnectionCallback), JdbcTemplate#query, JdbcTemplate#update
| Modifier and Type | Method and Description |
|---|---|
| public T | Returns: a result object, ornull if noneactive JDBC Connection con)Gets called by |
| doInConnection | back to summary |
|---|---|
| public T doInConnection(Connection con) throws SQLException, DataAccessException Gets called by If called without a thread-bound JDBC transaction (initiated by DataSourceTransactionManager), the code will simply get executed on the JDBC connection with its transactional semantics. If JdbcTemplate is configured to use a JTA-aware DataSource, the JDBC Connection and thus the callback code will be transactional if a JTA transaction is active. Allows for returning a result object created within the callback, i.e.
a domain object or a collection of domain objects. Note that there's special
support for single step actions: see
| |