Introduction to Spring: Why Spring? Replaceable Objects!

Written By Rick Hightower CTO of ArcMind

Contributors: Thomas Bridges (Qualcomm Inc.), Alex Redington, Kris Diefenderfer and Drew Davidson.

Brought to you by ArcMind: Know the Next! Training, Consulting and Mentoring for Spring, Hibernate, JSF and much more!

  If you follow the latest developer trends then you've likely heard of Spring, IoC (Inversion of Control) containers and AOP (aspect-oriented programming). Like many developers, architects and development managers, however, you may not see where these technologies fit into your development efforts.

  In this paper, we'll begin to remedy that, with a hands-on introduction to Spring to understand the basics of IoC, AOP and Spring Templates. We start with a high-level overview and then later delve into some of the technical details with plenty of code samples so that the paper is useful for developers, architects and development managers.

Why should you care?

• AOP can drastically reduce code that would otherwise be repeated.
• IoC allows you to easily assemble objects with their collaborators getting rid of so called wring code that typically occupies 30% or more of many code bases.
• Spring Templates take common, error prone code and encapsulates the logic for resource management and tricky exception handling so it can be reused, thus reducing the possibilities of defects that leak resources.
• Download paper here