Search:

Thanks. For some reason I had spring-tx and spring-jdbc running version 3.0.7.RELEASE. Added them to pom.xml and was fixed! The problem was spring-tx, which has those dao classes.

I'm using Spring 3.2.0.RELEASE with Spring Security 3.1.3.RELEASE and came across that error while trying to handle an empty result exception and I have no idea why...

Thanks in advance for any...