Author: buildbot
Date: Mon Dec 15 16:19:53 2014
New Revision: 932850
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/component-parameters.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/component-parameters.html
==============================================================================
--- websites/production/tapestry/content/component-parameters.html (original)
+++ websites/production/tapestry/content/component-parameters.html Mon Dec 15
16:19:53 2014
@@ -155,11 +155,11 @@
<h3><a shape="rect" name="ComponentParameters-Contents"></a>Contents</h3>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1418656788408 {padding: 0px;}
-div.rbtoc1418656788408 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1418656788408 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1418660381193 {padding: 0px;}
+div.rbtoc1418660381193 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1418660381193 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1418656788408">
+/*]]>*/</style><div class="toc-macro rbtoc1418660381193">
<ul class="toc-indentation"><li>Related Articles</li><li><a shape="rect"
href="#ComponentParameters-Contents">Contents</a></li></ul>
<ul><li><a shape="rect"
href="#ComponentParameters-ParameterBindings">Parameter Bindings</a></li><li><a
shape="rect" href="#ComponentParameters-BindingExpressions">Binding
Expressions</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#ComponentParameters-RenderVariables:Bindings">Render Variables:
Bindings</a></li><li><a shape="rect"
href="#ComponentParameters-Property:Bindings">Property: Bindings</a></li><li><a
shape="rect" href="#ComponentParameters-Validate:Bindings">Validate:
Bindings</a></li><li><a shape="rect"
href="#ComponentParameters-Translate:Bindings">Translate:
Bindings</a></li><li><a shape="rect"
href="#ComponentParameters-Asset:Bindings">Asset: Bindings</a></li><li><a
shape="rect" href="#ComponentParameters-Context:Bindings">Context:
Bindings</a></li></ul>
@@ -171,7 +171,7 @@ div.rbtoc1418656788408 li {margin-left:
<t:pagelink page="Index">Go Home</t:pagelink>
</html>
]]></script>
-</div></div><p>A component may have any number of parameters. Each parameter
has a specific name, a specific Java type (which may be a primitive value), and
may be <em>optional</em> or <em>required</em>.</p><p>Within a component class,
parameters are declared by using the @<a shape="rect" class="external-link"
href="http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Parameter.html";>Parameter</a>
annotation on a private field.</p><p><span class="confluence-anchor-link"
id="ComponentParameters-bindingparameters"></span></p><h1
id="ComponentParameters-ParameterBindings">Parameter Bindings</h1><p>In
Tapestry, a parameter is not a slot into which data is pushed: it is a
<em>connection</em> between a field of the component (marked with the
@Parameter annotation) and a property or resource of the component's container.
(Components can be nested, so the container can be either the page or another
component.)</p><p>The connection between a component and a property (o
r resource) of its container is called a <em>binding</em>. The binding is
two-way: the component can read the bound property by reading its parameter
field. Likewise, a component that updates its parameter field will update the
bound property.</p><p>This is important in a lot of cases; for example a
TextField component can read <em>and update</em> the property bound to its
value parameter. It reads the value when rendering, but updates the value when
the form is submitted.</p><p>The component listed below is a looping component;
it renders its body a number of times, defined by its <code>start</code> and
<code>end</code> parameters (which set the boundaries of the loop). The
component can update a <code>result</code> parameter bound to a property of its
container; it will automatically count up or down depending on whether
<code>start</code> or <code>end</code> is larger.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>A component may have any number of parameters. Each parameter
has a specific name, a specific Java type (which may be a primitive value), and
may be <em>optional</em> or <em>required</em>.</p><p>Within a component class,
parameters are declared by using the @<a shape="rect" class="external-link"
href="http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Parameter.html";>Parameter</a>
annotation on a private field, as we'll see below.</p><p><span
class="confluence-anchor-link"
id="ComponentParameters-bindingparameters"></span></p><h1
id="ComponentParameters-ParameterBindings">Parameter Bindings</h1><p>In
Tapestry, a parameter is not a slot into which data is pushed: it is a
<em>connection</em> between a field of the component (marked with the
@Parameter annotation) and a property or resource of the component's container.
(Components can be nested, so the container can be either the page or another
component.)</p><p>The connection between a compone
nt and a property (or resource) of its container is called a <em>binding</em>.
The binding is two-way: the component can read the bound property by reading
its parameter field. Likewise, a component that updates its parameter field
will update the bound property.</p><p>This is important in a lot of cases; for
example a TextField component can read <em>and update</em> the property bound
to its value parameter. It reads the value when rendering, but updates the
value when the form is submitted.</p><p>The component listed below is a looping
component; it renders its body a number of times, defined by its
<code>start</code> and <code>end</code> parameters (which set the boundaries of
the loop). The component can update a <code>result</code> parameter bound to a
property of its container; it will automatically count up or down depending on
whether <code>start</code> or <code>end</code> is larger.</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelConte
nt pdl">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><