Spring Framework 1.2.x Changelog
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" callback 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's0 码力 | 94 页 | 267.57 KB | 1 年前3Spring Framwork Data Access v5.3.36 SNAPSHOT
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 3.4.2. Using DataSourceUtils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . of 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 has0 码力 | 197 页 | 2.76 MB | 1 年前3Spring Framework 1.2.7 Changelog
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" callback 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 springframework.jdbc * deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface, allowing0 码力 | 87 页 | 248.22 KB | 1 年前3Spring Framework 1.2.8 Changelog
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" callback 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 springframework.jdbc * deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface, allowing0 码力 | 89 页 | 254.65 KB | 1 年前3Spring Framework 1.2.6 Changelog
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 springframework.jdbc * deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface, allowing sql-error-codes.xml * added "getTargetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect given target0 码力 | 83 页 | 236.45 KB | 1 年前3Spring Framework 1.2.0 Changelog
springframework.jdbc * deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface, allowing sql-error-codes.xml * added "getTargetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect given target 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 open0 码力 | 67 页 | 194.16 KB | 1 年前3Spring Framework 1.2.2 Changelog
springframework.jdbc * deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface, allowing sql-error-codes.xml * added "getTargetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect given target 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 open0 码力 | 72 页 | 205.76 KB | 1 年前3Spring Framework 1.2.1 Changelog
springframework.jdbc * deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface, allowing sql-error-codes.xml * added "getTargetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect given target 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 open0 码力 | 69 页 | 197.87 KB | 1 年前3Spring Framework 1.2.3 Changelog
springframework.jdbc * deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface, allowing sql-error-codes.xml * added "getTargetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect given target 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 open0 码力 | 74 页 | 215.40 KB | 1 年前3Spring Framework 1.2.5 Changelog
springframework.jdbc * deprecated "closeConnectionIfNecessary" method in favor of "releaseConnection" (in DataSourceUtils and JdbcDaoSupport) * added "releaseConnection" method to ConnectionHandle interface, allowing sql-error-codes.xml * added "getTargetConnection" method to DataSourceUtils, returning the innermost target Connection of a given proxy * refined DataSourceUtils' "closeConnectionIfNecessary" to detect given target 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 open0 码力 | 79 页 | 226.37 KB | 1 年前3
共 84 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9