<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<!-- We need a doctype to allow us to use special characters like &nbsp;
We use a "strict" DTD to make IE follow the alignment rules. -->
<html xmlns:t="http://tapestry.apache.org/schema/tapestry_5_4.xsd">
<body class="container">
<h3>Methods</h3>
As a page renders, it goes through phases. You can provide methods that Tapestry will call in those phases.
Here are the most useful ones...<br/><br/>
<ul>
<li>
<code>onActivate()</code>
Tapestry will call it when a request from a browser involves your page. <br /> Behind the scenes, what happens is
that Tapestry gets an instance of the page and triggers <em>activate</em> on it.
</li>
<li>
<code>setupRender()</code>
Tapestry will call it right before it starts rendering.
</li>
<li>
<code>cleanupRender()</code>
Tapestry will call it immediately after all the rendering has been done.
</li>
</ul>
Here is a demonstration:
<div class="eg">
message: "${message}".
</div>
Why is "cleanupRender() called..." missing from the message? Because the message is rendered BEFORE
<code>cleanupRender()</code> is called. However, "cleanupRender() called..." will be in the log.<br/><br/>
References:
<a href="http://tapestry.apache.org/component-rendering.html#ComponentRendering-RenderingPhases">Rendering Phases</a>,
<a href="http://tapestry.apache.org/component-rendering.html#ComponentRendering-SetupRender">SetupRender</a>,
<a href="http://tapestry.apache.org/component-rendering.html#ComponentRendering-CleanupRender">CleanupRender</a>.<br/><br/>
<t:pagelink page="Index">Home</t:pagelink><br/><br/>
<t:tabgroup>
<t:sourcecodetab src="/web/src/main/java/jumpstart/web/pages/examples/lang/Methods.tml"/>
<t:sourcecodetab src="/web/src/main/java/jumpstart/web/pages/examples/lang/Methods.java"/>
<t:sourcecodetab src="/web/src/main/resources/META-INF/assets/css/examples/olive.css"/>
</t:tabgroup>
</body>
</html>