You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by bu...@apache.org on 2013/02/10 12:20:53 UTC
svn commit: r850115 - in /websites/production/tapestry/content:
cache/main.pageCache tapestry-ioc-overview.html
Author: buildbot
Date: Sun Feb 10 11:20:53 2013
New Revision: 850115
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/tapestry-ioc-overview.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/tapestry-ioc-overview.html
==============================================================================
--- websites/production/tapestry/content/tapestry-ioc-overview.html (original)
+++ websites/production/tapestry/content/tapestry-ioc-overview.html Sun Feb 10 11:20:53 2013
@@ -52,6 +52,7 @@
<div id="breadcrumbs">
<a href="index.html">Apache Tapestry</a> > <a href="documentation.html">Documentation</a> > <a href="user-guide.html">User Guide</a> > <a href="ioc.html">IoC</a> > <a href="tapestry-ioc-overview.html">Tapestry IoC Overview</a>
+ <a class="edit" title="Edit this page (requires approval -- just ask on the mailing list)" href="https://cwiki.apache.org/confluence/pages/editpage.action?pageId=23338486">edit</a>
</div>
<div id="content">
@@ -67,13 +68,13 @@ table.ScrollbarTable td.ScrollbarNextIco
<h1><a shape="rect" name="TapestryIoCOverview-TapestryIoCOverview"></a>Tapestry IoC Overview</h1>
-<p>Even today, with the overwhelming success of <a shape="rect" class="external-link" href="http://www.springframework.org" >Spring</a> 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.</p>
+<p>Even today, with the overwhelming success of <a shape="rect" class="external-link" href="http://www.springframework.org" >Spring</a> and the rise of smaller, simpler approaches to building applications (in contrast to the heavyweight EJB approach), many people still have trouble wrapping their heads around Inversion of Control.</p>
<p>Really understanding IoC is a new step for many developers. If you can remember back to when you made the transition from procedural programming (in C, or BASIC) to object oriented programming, you might remember the point where you "got it". The point where it made sense to have methods on objects, and data inside objects.</p>
-<p>Inversion of Control builds upon those ideas. The goal is to make coding more robust (that is, with fewer errors), more reusable and to make code much easier to test.</p>
+<p>Inversion of Control builds upon those ideas. The goal is to make code more robust (that is, with fewer errors), more reusable and much easier to test.</p>
-<p>Most developers are used to a more <em>monolithic</em> design, they have a few core objects and a <tt>main()</tt> method somewhere that starts the ball rolling. <tt>main()</tt> instantiates the first couple of classes, and those classes end up instantiating and using all the other classes in the system.</p>
+<p>Prior to IoC approaches, most developers were used to a more <em>monolithic</em> design, with a few core objects and a <tt>main()</tt> method somewhere that starts the ball rolling. <tt>main()</tt> instantiates the first couple of classes, and those classes end up instantiating and using all the other classes in the system.</p>
<p>That's an <em>unmanaged</em> system. Most desktop applications are unmanaged, so it's a very familiar pattern, and easy to get your head around.</p>