I really liked the Dependency Injection part of Spring.
I have written code like those in the Spring Framework numerous times. I'm really glad I don't have to write those again.
(In response to the question "Don't all this DI stuff make the whole thing harder to comprehend?") Object-orientation itself makes the code harder to comprehend. What you get when you use Spring is that it naturally encourages a good OO architecture, where each component or layer does its own thing very well.
There is an XDoclet module that allows you to put how you want to inject the dependency into a class in Javadoc comments of the class, and generate the configuration XML that way. That's the inverse of Dependency Injection and not the right thing to do.
I'll update this blog when the presentation slides have been uploaded to our web site.
Prior to the talk, we had the usual recruiter introductions and the Q&A. Six recruiters stood up.
Hi, I'm Daugherty Business Systems, we are hiring.
Hi, I'm Jane Bullington from OCI. We have SIXTEEN Java positions, from senior J2EE architects to web developers. Give me a call.
Hi, I'm Technology Partners. Same story. Lots of Java openings.
Hi, I'm the Chief Technology Officer of MetaMatrix. We are looking for several Java talent.