correctly closes borrowed connections even for nested JDBC executions * DefaultJdoDialect supports JDO 3.0 query timeout facility (as supported by DataNucleus 2.1) * transaction names based on method id from for direct field access with ConversionService * @InitBinder methods support all applicable Spring 3.0 parameter annotations as well * fixed @RequestParam(required=false) regression for @InitBinder methods T(S) lookup if no explicit S->T converter matches * AbstractExcelView is compatible with Apache POI 3.0 as well as 3.5 now * TilesConfigurer only sets up EL support if JSP 2.1 is present (for JSP 2.0 compatibility)

for direct field access with ConversionService * @InitBinder methods support all applicable Spring 3.0 parameter annotations as well * fixed @RequestParam(required=false) regression for @InitBinder methods T(S) lookup if no explicit S->T converter matches * AbstractExcelView is compatible with Apache POI 3.0 as well as 3.5 now * TilesConfigurer only sets up EL support if JSP 2.1 is present (for JSP 2.0 compatibility) 3.0.0.M3 (2009-05-06) ---------------------------------------- * Spring 3.0 includes reference documentation now * Spring 3.0 is shipping with proper Maven POMs now * updated to JRuby 1.2 (remaining compatible

T(S) lookup if no explicit S->T converter matches * AbstractExcelView is compatible with Apache POI 3.0 as well as 3.5 now * TilesConfigurer only sets up EL support if JSP 2.1 is present (for JSP 2.0 compatibility) 3.0.0.M3 (2009-05-06) ---------------------------------------- * Spring 3.0 includes reference documentation now * Spring 3.0 is shipping with proper Maven POMs now * updated to JRuby 1.2 (remaining compatible basic JAX-RPC support only (next to JAX-WS) * introduced explicit XML array element in spring-beans-3.0.xsd * introduced new type conversion SPI and converter API in spring-core convert package * introduced

correctly closes borrowed connections even for nested JDBC executions * DefaultJdoDialect supports JDO 3.0 query timeout facility (as supported by DataNucleus 2.1) * transaction names based on method id from for direct field access with ConversionService * @InitBinder methods support all applicable Spring 3.0 parameter annotations as well * fixed @RequestParam(required=false) regression for @InitBinder methods T(S) lookup if no explicit S->T converter matches * AbstractExcelView is compatible with Apache POI 3.0 as well as 3.5 now * TilesConfigurer only sets up EL support if JSP 2.1 is present (for JSP 2.0 compatibility)

T(S) lookup if no explicit S->T converter matches * AbstractExcelView is compatible with Apache POI 3.0 as well as 3.5 now * TilesConfigurer only sets up EL support if JSP 2.1 is present (for JSP 2.0 compatibility) 3.0.0.M3 (2009-05-06) ---------------------------------------- * Spring 3.0 includes reference documentation now * Spring 3.0 is shipping with proper Maven POMs now * updated to JRuby 1.2 (remaining compatible basic JAX-RPC support only (next to JAX-WS) * introduced explicit XML array element in spring-beans-3.0.xsd * introduced new type conversion SPI and converter API in spring-core convert package * introduced

for direct field access with ConversionService * @InitBinder methods support all applicable Spring 3.0 parameter annotations as well * fixed @RequestParam(required=false) regression for @InitBinder methods T(S) lookup if no explicit S->T converter matches * AbstractExcelView is compatible with Apache POI 3.0 as well as 3.5 now * TilesConfigurer only sets up EL support if JSP 2.1 is present (for JSP 2.0 compatibility) 3.0.0.M3 (2009-05-06) ---------------------------------------- * Spring 3.0 includes reference documentation now * Spring 3.0 is shipping with proper Maven POMs now * updated to JRuby 1.2 (remaining compatible

correctly closes borrowed connections even for nested JDBC executions * DefaultJdoDialect supports JDO 3.0 query timeout facility (as supported by DataNucleus 2.1) * transaction names based on method id from for direct field access with ConversionService * @InitBinder methods support all applicable Spring 3.0 parameter annotations as well * fixed @RequestParam(required=false) regression for @InitBinder methods T(S) lookup if no explicit S->T converter matches * AbstractExcelView is compatible with Apache POI 3.0 as well as 3.5 now * TilesConfigurer only sets up EL support if JSP 2.1 is present (for JSP 2.0 compatibility)

correctly closes borrowed connections even for nested JDBC executions * DefaultJdoDialect supports JDO 3.0 query timeout facility (as supported by DataNucleus 2.1) * transaction names based on method id from for direct field access with ConversionService * @InitBinder methods support all applicable Spring 3.0 parameter annotations as well * fixed @RequestParam(required=false) regression for @InitBinder methods T(S) lookup if no explicit S->T converter matches * AbstractExcelView is compatible with Apache POI 3.0 as well as 3.5 now * TilesConfigurer only sets up EL support if JSP 2.1 is present (for JSP 2.0 compatibility)

zer subclass and override its configure method. Doing so makes use of Spring Framework’s servlet 3.0 support and lets you configure your application when it is launched by the servlet container. Typically bannerMode(Banner.Mode.OFF) } } } Applications can fall into more than one category: • Servlet 3.0+ applications with no web.xml. • Applications with a web.xml. • Applications with a context hierarchy each might require slightly different techniques. Servlet 3.0+ applications might translate pretty easily if they already use the Spring Servlet 3.0+ initializer support classes. Normally, all the code from

zer subclass and override its configure method. Doing so makes use of Spring Framework’s servlet 3.0 support and lets you configure your application when it is launched by the servlet container. Typically bannerMode(Banner.Mode.OFF) } } } Applications can fall into more than one category: • Servlet 3.0+ applications with no web.xml. • Applications with a web.xml. • Applications with a context hierarchy each might require slightly different techniques. Servlet 3.0+ applications might translate pretty easily if they already use the Spring Servlet 3.0+ initializer support classes. Normally, all the code from