log4p

About two weeks ago I migrated our project from spring 2.0.2 to the latest version available version in the maven repository at that time 2.0.4. The transition was smooth. It took a couple of days before I started realizing that the strange bugs (mostly in binding of primitives) surfacing in tested/accepted code where probably related to this version change.
I reread the changelogs for 2.0.4 and the only suspicious change seemed to be the following,

PropertyEditorRegistrySupport/BeanWrapperImpl lazily registers default editors when needed (to avoid init overhead)

But I wasn’t sure, didn’t have much time for a thorough investigation. This morning when we discovered even more unexplainable bugs I decided to upgrade to the latest stable version 2.0.5.

Even though there is nothing related to binding in the changelogs of 2.0.5 upgrading fixed our problem. Scary stuff! I started adding/extending a couple of unittests to be able to detect problems in the binding mechanism so I can verify their correct functioning in the future.