Given its dynamic aspect, Spring Framework is very skilled in hiding the real problem behind an obscure exception. Last evening, I had to stay at work later than usual in order to make the project's programmer tests (unit tests) run (The same tests ran on a colleagues machine by the way). It turned out that the problem was in a third party dependency. I had to add Apache Commons Collections JAR into my CLASSPATH. Grrrr!
Comments