avoiding side effects caused by getters * added "setExtractOldValueForEditor" method to BeanWrapper and BeanWrapperImpl, allowing to control setter invocation * BeanWrapperImpl's "getPropertyType" "PropertyDescriptor" method to BeanUtils, as alternative to retrieving the descriptors via a BeanWrapper * added "fileEncoding" and "propertiesPersister" properties to PropertyResourceConfigurer "factory-bean" attribute twice * factored out AbstractAutoWireCapableBeanFactory's BeanWrapper creation into protected "createBeanWrapper" method * fixed DefaultListableBeanFactory's

well Package org.springframework.beans $ ^{*} $ BeanWrapper doesn't iterate over Collection/Map if no generic type declared and * BeanWrapper converts an empty String to null in case of a Java allows for caching for specific ClassLoaders even if their classes are not cache-safe $ ^{*} $ BeanWrapper interface extends TypeConverter interface, instead of just $ ^{*} $ BeanWrapperImpl converts * factored out extended PropertyController and ConfigurablePropertyController interfaces from BeanWrapper/BeanWrapperImpl * BeanWrapperImpl supports PropertyEditors exposed by PropertyDescriptors (typically

binding, validation and the BeanWrapper ..... 40 4.1. Introduction ..... 40 4.2. Binding data using the DataBinder ..... 40 4.3. Bean manipulation and the BeanWrapper ..... 40 4.3.1. Setting and property editors, through their use of something called a BeanWrapper to handle property conversions. The standard property editors that the BeanWrapper registers are listed in the next chapter. Additionally oryLocator if there is a need. # Chapter 4. PropertyEditors, data binding, validation and the BeanWrapper #### 4.1. Introduction The big question is whether or not validation should be considered business

binding, validation and the BeanWrapper ..... 39 4.1. Introduction ..... 39 4.2. Binding data using the DataBinder ..... 39 4.3. Bean manipulation and the BeanWrapper ..... 39 4.3.1. Setting and property editors, through their use of something called a BeanWrapper to handle property conversions. The standard property editors that the BeanWrapper registers are listed in the next chapter. Additionally oryLocator if there is a need. # Chapter 4. PropertyEditors, data binding, validation and the BeanWrapper #### 4.1. Introduction The big question is whether or not validation should be considered business

binding, validation and the BeanWrapper ..... 40 4.1. Introduction ..... 40 4.2. Binding data using the DataBinder ..... 40 4.3. Bean manipulation and the BeanWrapper ..... 40 4.3.1. Setting and property editors, through their use of something called a BeanWrapper to handle property conversions. The standard property editors that the BeanWrapper registers are listed in the next chapter. Additionally oryLocator if there is a need. # Chapter 4. PropertyEditors, data binding, validation and the BeanWrapper #### 4.1. Introduction The big question is whether or not validation should be considered business

binding, validation and the BeanWrapper ..... 36 4.1. Introduction ..... 36 4.2. Binding data using the DataBinder ..... 36 4.3. Bean manipulation and the BeanWrapper ..... 36 4.3.1. Setting and oryLocator if there is a need. # Chapter 4. PropertyEditors, data binding, validation and the BeanWrapper #### 4.1. Introduction The big question is whether or not validation should be considered business MVC framework. The BeanWrapper is a fundamental concept in the Spring Framework and is used in a lot of places. However, you probably will not ever have the need to use the BeanWrapper directly. Because

binding, validation and the BeanWrapper ..... 42 4.1. Introduction ..... 42 4.2. Binding data using the DataBinder ..... 42 4.3. Bean manipulation and the BeanWrapper ..... 42 4.3.1. Setting and property editors, through their use of something called a BeanWrapper to handle property conversions. The standard property editors that the BeanWrapper registers are listed in the next chapter. Additionally oryLocator if there is a need. # Chapter 4. PropertyEditors, data binding, validation and the BeanWrapper #### 4.1. Introduction The big question is whether or not validation should be considered business

binding, validation and the BeanWrapper ..... 41 4.1. Introduction ..... 41 4.2. Binding data using the DataBinder ..... 41 4.3. Bean manipulation and the BeanWrapper ..... 41 4.3.1. Setting and property editors, through their use of something called a BeanWrapper to handle property conversions. The standard property editors that the BeanWrapper registers are listed in the next chapter. Additionally oryLocator if there is a need. # Chapter 4. PropertyEditors, data binding, validation and the BeanWrapper #### 4.1. Introduction The big question is whether or not validation should be considered business

BeanUtils skips conventional editor check for array classes (in order to not break AspectJ weaving) * BeanWrapper's introspection resolves bridge methods to find setter method for setter method with covariant class to default property editors * BeanWrapper explicitly finds default PropertyEditor according to "Editor" suffix convention * deprecated BeanWrapper's fallback to the global JavaBeans ry facade for obtaining BeanWrapper and direct field accessor instances * deprecated BeanWrapper's "setWrappedInstance" method in favor of recreating a BeanWrapper per target instance $

class to default property editors * BeanWrapper explicitly finds default PropertyEditor according to "Editor" suffix convention * deprecated BeanWrapper's fallback to the global JavaBeans ry facade for obtaining BeanWrapper and direct field accessor instances * deprecated BeanWrapper's "setWrappedInstance" method in favor of recreating a BeanWrapper per target instance $ AbstractAutoWireCapableBeanFactory's "applyBeanPropertyValues" fully initializes the BeanWrapper used for binding * AbstractAutowireCapableBeanFactory's "applyBeanPropertyValues"