I agree. I recently had to do some java work and had to come up to speed with Springs dependency injection. When it worked it was fine, but when something went

I agree. I recently had to do some java work and had to come up to speed with Springs dependency injection. When it worked it was fine, but when something went wrong there were so many layers of abstraction and vague error messages it was a nightmare to try and solve problems. I don't see what is wrong with the 'boring' way of dependency injection. If a class relies on another class, pass it in the constructor explicitly. It's simple and easy to follow the stack back to find problems.