I've done a lot of Spring side work and your first paragraph is the best explanation I've ever read for the framework. I also agree that if you can't test Spri

I've done a lot of Spring side work and your first paragraph is the best explanation I've ever read for the framework. I also agree that if you can't test Spring code you are doing something wrong. I get the frustration with having to create test harnesses for some things, and the SpringJ4Unit stuff oftentimes feels a bit too magical, but I've never seen well written Spring code that wasn't easily testable at the both the class and module functionality layer.