CustomEditorConfigurer functionality regression in 3.0 [SPR-5971] #10639
Description
Matthew Sgarlata opened SPR-5971 and commented
The CustomEditorConfigurer functions differently in Spring 3 than in earlier versions of Spring. The change may have been intentional or may have been accidental. Either way the reference document no longer matches the actual behavior of the class, so either the class needs to change or the reference document needs to change.
Here is the section of the reference document:
Here is the advertised usage pattern (and how it used to work before Spring 3):
<bean class="org.springframework.beans.factory.config.CustomEditorConfigurer">
<property name="customEditors">
<map>
<entry key="example.ExoticType">
<bean class="example.ExoticTypeEditor">
<property name="format" value="upperCase"/>
</bean>
</entry>
</map>
</property>
</bean>
Here is how it works in Spring 3:
<bean class="org.springframework.beans.factory.config.CustomEditorConfigurer">
<property name="customEditors">
<map>
<entry key="example.ExoticType" value="example.ExoticTypeEditor"/>
</map>
</property>
</bean>
Related bugs: 5773, 5860
Affects: 3.0 M3
Issue Links:
- CustomEditorConfigurer needs way to register Property Editor instances [SPR-5860] #10529 CustomEditorConfigurer needs way to register Property Editor instances
- XFire 1.2.6 not compatible with Spring 3.0's CustomEditorConfigurer [SPR-6157] #10825 XFire 1.2.6 not compatible with Spring 3.0's CustomEditorConfigurer
Referenced from: commits 6ffb750