{scrollbar}

Tapestry IoC Overview

Even today, with the overwhelming success of Spring and the rise of smaller, simpler approaches to building application that stand in sharp contrast to the ultra-heavyweight EJB approach, many people still have trouble wrapping their heads around Inversion of Control.

...

So we've come to accept that the death concern is better handled outside of our own code. The use of Inversion of Control is simply the flip side of that: the life cycle and construction concerns are also better handled by an outside authority as well: the IoC container. These concerns govern when a service is realized and how its dependencies and configuration are injected. As with the garbage collector, ceding these chores to the container results in less code and fewer bugs, and lets you concentrate on the things that should matter to you: your business logic, your application – and not a whole bunch of boilerplate plumbing!

{scrollbar}