tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From drobia...@apache.org
Subject svn commit: r918694 - /tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/configuration.apt
Date Wed, 03 Mar 2010 21:12:31 GMT
Author: drobiazko
Date: Wed Mar  3 21:12:28 2010
New Revision: 918694

URL: http://svn.apache.org/viewvc?rev=918694&view=rev
Fixed typos in the documentation of contribution methods.


Modified: tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/configuration.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/configuration.apt?rev=918694&r1=918693&r2=918694&view=diff
--- tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/configuration.apt (original)
+++ tapestry/tapestry5/trunk/tapestry-ioc/src/site/apt/configuration.apt Wed Mar  3 21:12:28
@@ -26,7 +26,7 @@
   A central service uses this configuration to select a particular FileService interface:
-  public static FileServicer buildFileServicerDispatcher(Map<String,FileServicer> contributions)
+  public static FileServiceDispatcher buildFileServicerDispatcher(Map<String,FileServicer>
     return new FileServiceDispatcherImpl(contributions);
@@ -35,7 +35,7 @@
   In order to provide a value for the contribution parameter, Tapestry will <collect>
   from service contribution methods. It will ensure that the keys and values match the generic
   types shown (String for the key, FileServicer for the value). The map will be assembled
and passed into
-  the service builder method, and from there, into the FileServiceDispatcherImpl contructor.
+  the service builder method, and from there, into the FileServiceDispatcherImpl constructor.
   So where do the values come from?  Service contributor methods, methods that start with

View raw message