Author: hlship
Date: Sat Jun 23 19:04:12 2007
New Revision: 550153
URL: http://svn.apache.org/viewvc?view=rev&rev=550153
Log:
TAPESTRY-1473: Rules for locating the component template for pages/components
in sub-packages needs to be documented and/or fixed
Modified:
tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/templates.apt
Modified:
tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/templates.apt
URL:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/templates.apt?view=diff&rev=550153&r1=550152&r2=550153
==============================================================================
--- tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/templates.apt
(original)
+++ tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/templates.apt Sat
Jun 23 19:04:12 2007
@@ -33,6 +33,11 @@
The location is based on the logical name of the page, in the previous
example, the template
would be <<<MyPage.html>>> in the root folder of the web application.
+ In certain cases, Tapestry will simplify the the logical name of a page. For
example, the page class
+ org.example.pages.address.CreateAddress will be given a logical name of
"address/Create" (the redundant "Address"
+ is removed as a suffix). However, this only affects how the page is
referenced in URLs; the template file
+ will still be CreateAddress.html, whether on the classpath, or as
WEB-INF/address/CreateAddress.html.
+
A template on the classpath takes precendence over a file in the web
application context.
Template Localization
