You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by bu...@apache.org on 2013/06/07 02:20:56 UTC
svn commit: r864716 - in /websites/production/tapestry/content:
cache/main.pageCache component-rendering.html
Author: buildbot
Date: Fri Jun 7 00:20:56 2013
New Revision: 864716
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/component-rendering.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/component-rendering.html
==============================================================================
--- websites/production/tapestry/content/component-rendering.html (original)
+++ websites/production/tapestry/content/component-rendering.html Fri Jun 7 00:20:56 2013
@@ -76,15 +76,15 @@
</td></tr><tr><td colspan="1" rowspan="1">
<span class="icon icon-page" title="Page">Page:</span>
- <a shape="rect" href="component-rendering.html">Component Rendering</a>
+ <a shape="rect" href="page-navigation.html">Page Navigation</a>
</td></tr><tr><td colspan="1" rowspan="1">
<span class="icon icon-page" title="Page">Page:</span>
- <a shape="rect" href="page-navigation.html">Page Navigation</a>
+ <a shape="rect" href="page-life-cycle.html">Page Life Cycle</a>
</td></tr><tr><td colspan="1" rowspan="1">
<span class="icon icon-page" title="Page">Page:</span>
- <a shape="rect" href="page-life-cycle.html">Page Life Cycle</a>
+ <a shape="rect" href="component-rendering.html">Component Rendering</a>
</td></tr></table>
</div>
@@ -324,6 +324,11 @@ Each of the orange phases (SetupRender,
</pre>
</div></div>
+<h2><a shape="rect" name="ComponentRendering-ShortCircuiting"></a>Short Circuiting</h2>
+
+<p>If a method returns a true or false value, this will short circuit processing. Other methods within the phase that would ordinarily be invoked will not be invoked.</p>
+
+<p>Most render phase methods should return void, to avoid unintentionally short circuiting other methods for the same phase.</p>
<h2><a shape="rect" name="ComponentRendering-MethodConflictsandOrdering"></a>Method Conflicts and Ordering</h2>
@@ -352,16 +357,25 @@ Each of the orange phases (SetupRender,
<ul><li>Subclass methods</li><li>Parent class methods</li><li>Mixin subclass methods</li><li>Mixin parent class methods</li></ul>
-<h2><a shape="rect" name="ComponentRendering-WithinaSingleClass"></a>Within a Single Class</h2>
+<h3><a shape="rect" name="ComponentRendering-WithinaSingleClass"></a>Within a Single Class</h3>
<p>Currently, rendering methods having the same annotation within a single class are executed in alphabetical order by method name. Methods with the same name are ordered by number of parameters. Even so, annotating multiple methods with the same rendering phase is not a great idea. Instead, just define one method, and have it call the other methods in the order you desire.</p>
-<h3><a shape="rect" name="ComponentRendering-ShortCircuiting"></a>Short Circuiting</h3>
+<h2><a shape="rect" name="ComponentRendering-RenderingComments"></a>Rendering Comments</h2>
-<p>If a method returns a true or false value, this will short circuit processing. Other methods within the phase that would ordinarily be invoked will not be invoked.</p>
+<p>Starting with version 5.3, Tapestry can optionally emit rendering comments for all requests; these are comments such as <!--BEGIN Index:loop (context:Index.tml, line 15)--> that can assist you in debugging markup output on the client-side. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.</p>
-<p>Most render phase methods should return void, to avoid unintentionally short circuiting other methods for the same phase.</p>
-</div>
+<p>Rendering comments are only available when not running in <a shape="rect" href="configuration.html#Configuration-tapestry.productionmode">production mode</a>.</p>
+
+<p>To turn on rendering comments for all requests, set the <a shape="rect" href="configuration.html#Configuration-tapestry.componentrendertracingenabled">tapestry.component-render-tracing-enabled</a> configuration symbol to "true".</p>
+
+<p>To turn on rendering comments only for a particular request, add the query parameter <tt>t:component-trace=true</tt> to the URL:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+ http:<span class="code-comment">//www.example.com/myapp/mypage?t:component-trace=<span class="code-keyword">true</span></span>
+</pre>
+</div></div></div>
</div>
<div class="clearer"></div>