Hi,

might be a bit late, but I just encountered the same exception while migrating an application from spring 2.5.6 to spring 3.0.5.RELEASE

In my case, the problem was coming from a transitive...