svn commit: r464068 - in /tapestry/tapestry5/tapestry-core/trunk/src/site/apt: guide/infrastructure.apt struts.apt

[hl...@apache.org]

Author: hlship
Date: Sat Oct 14 16:55:07 2006
New Revision: 464068

URL: http://svn.apache.org/viewvc?view=rev&rev=464068
Log:
Minor documentation tweaks.

Modified:
    tapestry/tapestry5/tapestry-core/trunk/src/site/apt/guide/infrastructure.apt
    tapestry/tapestry5/tapestry-core/trunk/src/site/apt/struts.apt

Modified: tapestry/tapestry5/tapestry-core/trunk/src/site/apt/guide/infrastructure.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/tapestry-core/trunk/src/site/apt/guide/infrastructure.apt?view=diff&rev=464068&r1=464067&r2=464068
==============================================================================
--- tapestry/tapestry5/tapestry-core/trunk/src/site/apt/guide/infrastructure.apt (original)
+++ tapestry/tapestry5/tapestry-core/trunk/src/site/apt/guide/infrastructure.apt Sat Oct 14 16:55:07 2006
@@ -47,11 +47,13 @@
   by default:
   
 *-----------------------+--------------------------------------------------------------------+------------------------------------+
-| <<Property>>          | <<Service Interfeace>>                                             | <<Default Service>>               |
+| <<Property>>          | <<Service Interface>>                                             | <<Default Service>>               |
 *-----------------------+--------------------------------------------------------------------+-----------------------------------+
 | request               | {{{../apidocs/org/apache/tapestry/services/WebRequest.html}WebRequest}}  | tapestry.WebRequest         |        
 *-----------------------+--------------------------------------------------------------------------------------------------------+
 | response | {{{../apidocs/org/apache/tapestry/services/WebResponse.html}WebResponse}}  | tapestry.WebResponse |        
+*-----------------------+--------------------------------------------------------------------------------------------------------+
+| typeCoercer | {{{../apidocs/org/apache/tapestry/ioc/services/TypeCoercer.html}TypeCoercer}}  | tapestry.ioc.TypeCoercer |        
 *-----------------------+--------------------------------------------------------------------------------------------------------+
 Default properties available via the infrastructure object provider
 

Modified: tapestry/tapestry5/tapestry-core/trunk/src/site/apt/struts.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/tapestry-core/trunk/src/site/apt/struts.apt?view=diff&rev=464068&r1=464067&r2=464068
==============================================================================
--- tapestry/tapestry5/tapestry-core/trunk/src/site/apt/struts.apt (original)
+++ tapestry/tapestry5/tapestry-core/trunk/src/site/apt/struts.apt Sat Oct 14 16:55:07 2006
@@ -106,7 +106,9 @@
   to redisplay the form with the error messages. The view has to <adapt> to the state
   determined by the request.
   
-  But what happens when the "fixture" has behavior? For example, maybe a fixture is a login form
+  But what happens when the "fixture" has its own behavior? It's own state?
+  
+  For example, maybe a fixture is a login form
   that's displayed on every page until the user logs in.  The form may have a URL that
   points to a login Action ... but how do you return to the same view after logging in?
   A similar case may be a component that displays tabular data and supports paging. Such
@@ -114,6 +116,14 @@
   return the user to the same view after changing the set of displayed items?  
   What if there's more than one such component in a single view?
   
-  It ends up being more and more configuration. You must define more and more JSP attributes
-  or other tricks in order to tell the appropriate action how to get the correct view
+  You end up writing more and more configuration and boilerplate code. 
+  You must define more and more JSP attributes
+  or other tricks in order to tell the appropriate action how to get the correct view after
+  performing the actions.
+  
+  You've run into the limitation of not having true web components on your side.
+  
+Tapestry: The Full Cycle Solution
+
+  <More to come ...>