the database ..... 108 10.3. Controlling how we connect to the database ..... 109 10.3.1. DataSourceUtils ..... 109 10.3.2. SmartDataSource ..... 109 10.3.3. AbstractDataSource ..... 109 10.3.4 this manual. ##### 7.3.2. Low-level approach At a lower level exist classes such as DataSourceUtils (for JDBC), SessionFactoryUtils (for Hibernate), PersistenceManagerFactoryUtils (for JDO), and would instead use Spring's org.springframework.jdbc.datasource.DataSourceUtils class as follows: Connection conn = DataSourceUtils.getConnection(dataSource); If an existing transaction exists, and

the database ..... 116 11.3. Controlling how we connect to the database ..... 117 11.3.1. DataSourceUtils ..... 117 11.3.2. SmartDataSource ..... 117 11.3.3. AbstractDataSource ..... 117 11.3.4 this manual. ##### 8.3.2. Low-level approach At a lower level exist classes such as DataSourceUtils (for JDBC), SessionFactoryUtils (for Hibernate), PersistenceManagerFactoryUtils (for JDO), and would instead use Spring's org.springframework.jdbc.datasource.DataSourceUtils class as follows: Connection conn = DataSourceUtils.getConnection(dataSource); If an existing transaction exists, and

Controlling Database Connections ..... 89 3.4.1. Using DataSource ..... 89 3.4.2. Using DataSourceUtils ..... 91 3.4.3. Implementing SmartDataSource ..... 91 3.4.4. Extending AbstractDataSource this reference documentation. ##### 1.3.2. Low-level Synchronization Approach Classes such as DataSourceUtils (for JDBC), EntityManagerFactoryUtils (for JPA), SessionFactoryUtils (for Hibernate), and so can instead use Spring's org.springframework.jdbc.datasource.DataSourceUtils class, as follows: Connection conn = DataSourceUtils.getConnection(dataSource); If an existing transaction already has

SQLErrorCodesFactory's access to the DataSource cache * refined DataSourceUtils to catch Throwable on "Connection.close()" * DataSourceUtils uses lower synchronization order for delegating handles (such Connection's class loader * fixed DataSourceUtils to correctly re-suspend a Connection even if the Connection hasn't been used since resume * refined DataSourceUtils to expect an "afterCompletion" assuming that the contained disconnected data is serializable * refined JTA synchronization in DataSourceUtils to release JDBC Connection on suspend (for JBoss JTA compatibility) * relaxed OracleLobHandler's

deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface xml * added "targetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect batchUpdate(String[] sql)" method to JdbcTemplate, for executing a group of SQL statements as a batch * DataSourceUtils only executes Connection cleanup in "beforeCompletion" synchronization if there are no

deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface xml * added "targetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect batchUpdate(String[] sql)" method to JdbcTemplate, for executing a group of SQL statements as a batch * DataSourceUtils only executes Connection cleanup in "beforeCompletion" synchronization if there are no

deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface xml * added "targetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect reference in case of "cacheHome"=false Package org.springframework.jdbc * deprecated DataSourceUtils' "dataSourceFromJndi" methods, in favor of fetching from JNDI via JndiObjectFactoryBean

declared on interfaces as well $ ^{*} $ removed deprecated BeanFactoryBootstrap class * refined DataSourceUtils to catch Throwable on "Connection.close()" $ ^{*} $ EhCacheManagerFactoryBean creates "prepareConnection" and "closeConnection" methods in SingleConnectionFactory * DataSourceUtils uses lower synchronization order for delegating handles (such as from TransactionAwareDataSourceProxy) springframework.jdbc * added further default SQL error codes for MS SQL, MySQL, and Oracle * refined DataSourceUtils to expect an "afterCompletion" callback from a different thread (in case of JTA transaction)

springframework.jca Package org.springframework.jdbc * refined DataSourceUtils to catch Throwable on "Connection.close()" * DataSourceUtils uses lower synchronization order for delegating handles (such springframework.jdbc * added further default SQL error codes for MS SQL, MySQL, and Oracle * refined DataSourceUtils to expect an "afterCompletion" callback from a different thread (in case of JTA transaction) (used by Spring Web Flow) ##### Changes in version 2.0 M1 (22.12.2005) ## Overall * fixed DataSourceUtils to correctly re-suspend a Connection even if the Connection hasn't been used since resume

deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface xml * added "targetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect reference in case of "cacheHome"=false Package org.springframework.jdbc * deprecated DataSourceUtils' "dataSourceFromJndi" methods, in favor of fetching from JNDI via JndiObjectFactoryBean