Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r733956 -
 /tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/service.apt
Date: Mon, 12 Jan 2009 23:05:25 -0000
To: commits@tapestry.apache.org
From: hlship@apache.org
Message-Id: <20090112230525.EF79F23888A5@eris.apache.org>

Author: hlship
Date: Mon Jan 12 15:05:25 2009
New Revision: 733956

URL: http://svn.apache.org/viewvc?rev=733956&view=rev
Log:
TAP5-386:Tapestry IoC documentation improvements

Modified:
    tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/service.apt

Modified: tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/service.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/service.apt?rev=733956&r1=733955&r2=733956&view=diff
==============================================================================
--- tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/service.apt (original)
+++ tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/service.apt Mon Jan 12 15:05:25 2009
@@ -182,9 +182,11 @@
   }
 +-----------------------------------------------------------------------------------+
 
-  Here we've annotated the parameters of the service builder method to identify what
-  service to inject for that parameter.  
-  
+  Tapestry assumes that parameters to builder methods are dependencies; in this example
+  it is able to figure out what services to pass in based just on the type (later we'll
+  see how we can fine tune this with annotations, when the service type is not sufficient
+  to identify a single service).
+
   This is an example of when you would want to use the service builder method, rather than
   just binding the service interface to the implementation class: because we want to do something extra,
   in this case, register the new indexer service with the scheduler.