Comments on: The Ideas in the Spring Framework

By: Sijin

Sijin — Fri, 27 Oct 2006 16:28:18 +0000

Right on regarding the “Program to an interface part”, see my post on a similar topic http://www.indiangeek.net/?p=41

By: Wes Maldonado: Data Junkie » Blog Archive » The Number One NIH Syndrome Sympton (or, How I learned to not invent wheels and learned to love 3rd party components.)

Thu, 26 Oct 2006 20:52:47 +0000

[…] I was happily reading The Ideas in the Spring Framework for Java that covered the basics of Dependency Injection using Spring and linked to another article, Dependency Injection without Frameworks… which screamed of NIH and slightly ruined my day. […]

By: Patrick Bourke

Patrick Bourke — Tue, 17 Oct 2006 11:11:34 +0000

“Spring advocates using setter methods instead of contructor arguments for setting properties”

While setter injection tends to appear more often in the Spring documentation, constructor injection is equally valid and fully supported. I find that constructor injection tends to minimise errors in object configuration. It allows you to validate required collaborators in a normal Java constructor, rather than creating some artificial “init” method or introducing a dependency on the framework. It also helps to limit the number of states that an object can occupy.

I agree with your points on AOP. Like many tools, it’s useful only insofar as it helps us to manage complexity.

By: 360731 Blog Verification

360731 Blog Verification — Tue, 17 Oct 2006 08:14:51 +0000

360731 Blog Verification…

360731…