change (rather than your code). 1.2. Understanding the Spring Framework Transaction Abstraction The key to the Spring transaction abstraction is the notion of a transaction strategy. A transaction strategy interface, which creates callable statements. The RowCallbackHandler interface extracts values from each row of a ResultSet. You can use JdbcTemplate within a DAO implementation through direct instantiation Queries Some query methods return a single value. To retrieve a count or a specific value from one row, use queryForObject(..). The latter converts the returned JDBC Type to the Java class that is passed

"requiredSingleResult" to never accept more than 1 row in result (as per its c.) * SqlQuery's "findObject" explicitly uses "singleResult" to never accept more than 1 row in result (as per its contract) Package it as batch size * added "trackRowsAffected" property to BatchSqlUpdate, allowing to turn off the row counts list to save memory Package org.springframework.jmx * fixed MBeanServerConnectionFactoryBean validation * BindException uses canonical bean property paths for error registration, allowing any map key syntax for error access * added convenience constructors to DataBinder, WebDataBinder and ServletRequestDataBinder

setPeople(java.util.Properties) call --> key="HarryPotter">The magic property key="JerrySeinfeld">The funny property 3