Hibernate 3.1) * turned JdbcTemplate's "query(PreparedStatementCreator, PreparedStatementSetter, ResultSetExtractor rse)" method public * improved JdbcTemplate's logging of ignored SQLWarnings SQLWarnings, including SQL state and error code in the log output * JdbcTemplate's "queryForObject"/"queryForInt" /etc methods correctly detect incorrect result sizes TransactionAwareDataSourceProxy works correctly in combination with JdbcTemplate and transaction suspend/resume now * fixed JdbcTemplate to extract the JDBC Connection for CallableStatementCreators if a

as well * JdbcTemplate creates LinkedHashMap (instead of plain HashMap) as default results Map returned from "call" operation * JdbcDaoSupport does not override specified JdbcTemplate on subsequent waiting in case of thread interruption * JdbcTemplate falls back to type VARCHAR for a null value in case of an unknown SQL type specified against IBM DB2 * JdbcTemplate uses "PreparedStatement.setString" GeneratedKeyHolder to avoid NPE in exception message in case of a null key returned by the JDBC driver * fixed JdbcTemplate's fallback support for batch updates to properly handle InterruptibleBatchPreparedStatementSetters

ReflectiveMethodResolver to avoid potential unsupportedOperationException on sort (SPR-10392) * JdbcTemplate defensively uses JDBC 3.0 getParameterType call for Oracle driver compatibility (SPR-10385) * DefaultLobHandler for the Oracle 10g driver and higher (SPR-10339) * deprecated (NamedParameter)JdbcTemplate's queryForInt/Long operations in favor of queryForObject (SPR-10257) * added useful query "countRowsInTableWhere()" and "dropTables()" in JdbcTestUtils (SPR-9235) * introduced JdbcTemplate in tx base classes in the TestContext framework (SPR-8990) * introduced "countRowsInTableWhere()"

3.3.1. Using JdbcTemplate ..... 71 Querying (SELECT) ..... 71 Updating (INSERT, UPDATE, and DELETE) with JdbcTemplate ..... 74 Other JdbcTemplate Operations ..... 75 JdbcTemplate Best Practices Practices ..... 76 3.3.2. Using NamedParameter JdbcTemplate ..... 79 3.3.3. Using SQLExceptionTranslator ..... 82 3.3.4. Running Statements ..... 84 3.3.5. Running Queries ..... 85 3.3.6. Updating the JdbcTransactionManager ..... 92 3.5. JDBC Batch Operations ..... 93 3.5.1. Basic Batch Operations with JdbcTemplate ..... 93 3.5.2. Batch Operations with a List of Objects ..... 95 3.5.3. Batch Operations with

实现BeanPostProcessor 2.7. 完成IoC容器 实现AOP 3.1. 实现ProxyResolver 3.2. 实现Around 实现JDBC和事务 4.1. 实现JdbcTemplate 4.2. 实现声明式事务 实现Web MVC 5.1. 启动IoC容器 5.2. 实现MVC 5.3. 开发Web应用 实现Boot 6.1. 启动嵌入式Tomcat 6.2. 开发Boot应用 Summer Framework设计目标如下： context模块：实现ApplicationContext容器与Bean的管理； aop模块：实现AOP功能； jdbc模块：实现JdbcTemplate，以及声明式事务管理； web模块：实现Web MVC和REST API; boot模块：实现一个简化版的“Spring Boot”，用于打包运行。 我们会一步一步实现各模块，并在此基础上开发完整的应用程序。 return new HikariDataSource(...); } @Bean JdbcTemplate createJdbcTemplate(...) { return new JdbcTemplate(...); } } } 基于Annotation配置的IoC容器基本用法就是上面所述。下面，我们就一步一步来实现IoC容器。

for delegating handles (such as * JdbcTemplate logs SQLWarnings at debug instead of warn level, to avoid repeated warn logs for acceptable conditions * JdbcTemplate uses "PreparedStatement.setObject(index unknown SQL type on Informix * JdbcTemplate by default uses "PreparedStatement.setString" for any CharSequence (including String and StringBuilder) * JdbcTemplate does not check static SQL for for bind parameters anymore, to avoid overhead of double parsing * JdbcTemplate's "queryForObject" uses "requiredSingleResult" to never accept more than 1 row in result (as per its

(e.g. from SUPPORTS) * JdbcTemplate applies "fetchSize" and "maxRows" settings to all created Statements, not just to "query" operations * JdbcTemplate exposes Connection proxy is null and type unknown * JdbcTemplate's "update" version with a KeyHolder argument explicitly closes the generated keys ResultSet, if any * removed JdbcTemplate's fetchSize/maxRows check transaction synchronization to correctly handle suspension even from beforeCompletion/afterCompletion * JdbcTemplate releases Connection early, to avoid potential connection pool deadlock due to SQLException translation

is null and type unknown * JdbcTemplate's "update" version with a KeyHolder argument explicitly closes the generated keys ResultSet, if any * removed JdbcTemplate's fetchSize/maxRows check "queryForRowSet" methods to JdbcTemplate, returning a SqlRowSet as generic representation of the result rows * added "queryForObject" convenience methods to JdbcTemplate, taking a RowMapper argument methods with "elementType" argument to JdbcTemplate, for extracting values from a single column * added "queryForMap" methods to JdbcTemplate, creating a Map representation for the columns

basic JDBC processing and error handling ..... 402 JdbcTemplate ..... 402 Examples of JdbcTemplate class usage ..... 402 JdbcTemplate best practices ..... 404 NamedParameterJdbcTemplate NativeJdbcExtractor ..... 414 19.4. JDBC batch operations ..... 415 Basic batch operations with the JdbcTemplate ..... 415 Batch operations with a List of objects ..... 416 Batch operations with ApplicationContext, for performing explicit bean lookups or testing the state of the context as a whole. • A JdbcTemplate, for executing SQL statements to query the database. Such queries can be used to confirm database

control basic JDBC processing and error handling ..... 410 JdbcTemplate ..... 410 Examples of JdbcTemplate class usage ..... 410 JdbcTemplate best practices ..... 412 NamedParameterJdbcTemplate .. NativeJdbcExtractor ..... 422 19.4. JDBC batch operations ..... 423 Basic batch operations with the JdbcTemplate ..... 423 Batch operations with a List of objects ..... 423 Batch operations with multiple ApplicationContext, for performing explicit bean lookups or testing the state of the context as a whole. • A JdbcTemplate, for executing SQL statements to query the database. Such queries can be used to confirm database