root 3.3.3.2. The null element The null element is used to handle null values. Spring treats empty arguments for properties and the like as empty code: exampleBean.setEmail(""). The special <null> element may be used to indicate a null value, so that: <null/> is equivalent to the the java code: exampleBean.setEmail(null). 3.3.3.3. The collection elements The list, set, map, and props elements allow properties and arguments of Java type List, Set, Map, and Properties, respectively

root 3.3.3.2. The null element The null element is used to handle null values. Spring treats empty arguments for properties and the like as empty code: exampleBean.setEmail(""). The special <null> element may be used to indicate a null value, so that: <null/> is equivalent to the the java code: exampleBean.setEmail(null). 3.3.3.3. The collection elements Beans, BeanFactory and the ApplicationContext Spring Framework Version 1.2.6 15 The list, set, map, and props elements allow

root 3.3.3.2. The null element The null element is used to handle null values. Spring treats empty arguments for properties and the like as empty code: exampleBean.setEmail(""). The special <null> element may be used to indicate a null value, so that: <null/> is equivalent to the the java code: exampleBean.setEmail(null). 3.3.3.3. The collection elements Beans, BeanFactory and the ApplicationContext Spring Framework Version 1.2.9 26 The list, set, map, and props elements allow

root 3.3.3.2. The null element The null element is used to handle null values. Spring treats empty arguments for properties and the like as empty code: exampleBean.setEmail(""). The special <null> element may be used to indicate a null value, so that: <null/> is equivalent to the the java code: exampleBean.setEmail(null). 3.3.3.3. The collection elements The list, set, map, and props elements allow properties and arguments of Java type List, Set, Map, and Properties, respectively

root 3.3.3.2. The null element The null element is used to handle null values. Spring treats empty arguments for properties and the like as empty code: exampleBean.setEmail(""). The special <null> element may be used to indicate a null value, so that: <null/> is equivalent to the the java code: exampleBean.setEmail(null). 3.3.3.3. The collection elements Beans, BeanFactory and the ApplicationContext Spring Framework Version 1.2.8 15 The list, set, map, and props elements allow

root 3.3.3.2. The null element The null element is used to handle null values. Spring treats empty arguments for properties and the like as empty code: exampleBean.setEmail(""). The special <null> element may be used to indicate a null value, so that: <null/> is equivalent to the the java code: exampleBean.setEmail(null). 3.3.3.3. The collection elements Beans, BeanFactory and the ApplicationContext Spring Framework Version 1.2.4 15 The list, set, map, and props elements allow

root 3.3.3.2. The null element The null element is used to handle null values. Spring treats empty arguments for properties and the like as empty code: exampleBean.setEmail(""). The special <null> element may be used to indicate a null value, so that: <null/> is equivalent to the the java code: exampleBean.setEmail(null). 3.3.3.3. The collection elements Beans, BeanFactory and the ApplicationContext Spring Framework Version 1.2.7 15 The list, set, map, and props elements allow

root 3.3.3.2. The null element The null element is used to handle null values. Spring treats empty arguments for properties and the like as empty code: exampleBean.setEmail(""). The special <null> element may be used to indicate a null value, so that: <null/> is equivalent to the the java code: exampleBean.setEmail(null). 3.3.3.3. The collection elements Beans, BeanFactory and the ApplicationContext Spring Framework Version 1.2.5 15 The list, set, map, and props elements allow

properly detect JDK 1.6/1.7 (Java 6/7) as higher than 1.5 (Java 5) * fixed SpringVersion to return null if the package is not determinable because of ClassLoader restrictions * fixed PathMatchingResourcePatternResolver warn logs for acceptable conditions * JdbcTemplate uses "PreparedStatement.setObject(index, null)" for null values with unknown SQL type on Informix * JdbcTemplate by default uses "PreparedStatement.setString" constract details * CharacterEncodingFilter only applies its encoding if actually specified (non- null) * WebDataBinder explicitly suppresses field marker prefix values in case of "ignoreUnknownFields"

Package org.springframework.aop * AbstractAutoProxyCreator (as used by "aop:config") correctly ignores null bean instances * "aop:aspect" doesn't insist on aspect bean reference to be specified when just SmartInstantiationAwareBeanPostProcessor's "determineCandidateConstructors" is only invoked for non-null bean Class * ServiceLocatorFactoryBean handles equals and hashCode based on proxy object identity a generic superclass method * @ModelAttribute annotated handler method arguments can resolve to a null value as well (when contained in the model) * standard method argument subtypes (such as a Principal