Dependency Injection and Inversion of Control - Java-Springs

Java applications -- a loose term that runs the gamut from constrained applets to n-tier server-side enterprise applications -- typically consist of objects that collaborate to form the application proper.Thus the objects in an application have dependencies on each other.

Although the Java platform provides a wealth of application development functionality,it lacks the means to organize the basic building blocks into a coherent whole, leaving that task to architects and developers.

True, you can use design patterns such as Factory, Abstract Factory, Builder, Decorator, and Service Locator to compose the various classes and object instances that make up an application.However, thesepatterns are simply that: best practices given a name, with a description of what the pattern does, where toapply it, the problems it addresses,and so forth.Patterns are formalized best practices that you must implement yourself in your application.

The Spring Framework Inversion of Control (IoC) component addresses this concern by providing a formalized means of composing disparate components into a fully working application ready for use.The Spring Framework codifies formalized design patterns as first-class objects that you can integrate into your own application(s).Numerous organizations and institutions use the Spring Framework in this manner to engineer robust, maintainable applications.