To use the contextual session approach, your DAO methods require access to the session factory, which can be injected via a setter method or a constructor argument.

The second callback interface, PreparedStatementSetter, as its name indicates, performs only the parameter binding task of the
overall update process.

In Hibernate, the core interface for object persistence is Session, whose instances can be obtained from a SessionFactory instance.

Derby can run in either the embedded mode or the client/server mode.

SimpleJdbcTemplate offers a convenient batch update method for you to specify a SQL statement and a batch of parameters in the form of List so that you don't need to implement the BatchPreparedStatementSetter interface.

To access a database running on the Derby server, you have to the Derby client library to your CLASSPATH.

These behaviors are defined in the org.springframework.transaction.TransactionDefinition interface.