If you have an application with thousand of beans, you must do unit testing but…Spring testing is boring, belive me. A very complex Spring application usually have a lot of dependency: I had to manage over 3000 beans definitions in a production project right now. Sometimes you want only to test a bit of it, and setting up a complete Spring Context will drive you crazy. To avoid losing mind, my suggestion is to …cheat. Let’see how.

Read More

Inversion of Control (IoC) is a very good idea.

But as the clever Joel Spolsky  noted, sometimes you need to be a super-natural hero to use it:

… I try not to be judgemental (HAHA!), but I think that people who use IoC containers are (A) very smart and (B) lacking in empathy for people who aren't as smart as they are. Everything makes perfect sense to them, so they have trouble understanding that many ordinary programmers will find the concepts confusing. It's the curse of knowledge. The people who understand IoC containers have trouble believing that there are people who don't understand it. …

I have trouble using Spring in at least two projects. On the third, it was a disaster, because a single software-architect-guy keeps passing around the Spring context factory as method parameter, getting beans from it!
Read More