Author: buildbot
Date: Mon Jul 27 12:19:44 2015
New Revision: 959757
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/component-classes.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/component-classes.html
==============================================================================
--- websites/production/tapestry/content/component-classes.html (original)
+++ websites/production/tapestry/content/component-classes.html Mon Jul 27
12:19:44 2015
@@ -195,7 +195,7 @@ public class Countdown
private int countValue;
}
</pre>
-</div></div><p>The above defines a component whose embedded id is "count"
(this id is derived from the name of the field and an element with that id must
be present in the corresponding template, otherwise an error is displayed (see
below)). The type of the component is org.example.app.components.Count. The
start and end parameters of the Count component are bound to literal values,
and the value parameter of the Count component is bound to the countValue
property of the Countdown component.</p><p>Technically, the start and end
parameters should be bound to properties, just the the value parameter.
However, certain literal values, such as the numeric literals in the example,
are accepted by the <code>prop:</code> binding prefix even though they are not
actually properties (this is largely as a convenience to the application
developer). We could also use the <code>literal:</code> prefix,
<code>"start=literal:5"</code>, which accomplishes largely the same
thing.</p><p>You may specify
additional parameters inside the component template, but parameters in the
component class take precedence.</p><p><strong>TODO: May want a more complex
check; what if user uses prop: in the template and there's a
conflict?</strong></p><p>You may override the default component id (as derived
from the field name) using the id() attribute of the Component
annotation.</p><p>If you define a component in the component class, and there
is no corresponding element in the template, Tapestry will log an error. In the
example above that would be the case if the template for the Countdown page
didn't contain an element with <code><t:count
t:id="count"></code>.</p></div>
+</div></div><p>The above defines a component whose embedded id is "count"
(this id is derived from the name of the field and an element with that id must
be present in the corresponding template, otherwise an error is displayed (see
below)). The type of the component is org.example.app.components.Count. The
start and end parameters of the Count component are bound to literal values,
and the value parameter of the Count component is bound to the countValue
property of the Countdown component.</p><p>Technically, the start and end
parameters should be bound to properties, just like the value parameter.
However, certain literal values, such as the numeric literals in the example,
are accepted by the <code>prop:</code> binding prefix even though they are not
actually properties (this is largely as a convenience to the application
developer). We could also use the <code>literal:</code> prefix,
<code>"start=literal:5"</code>, which accomplishes largely the same
thing.</p><p>You may specify
additional parameters inside the component template, but parameters in the
component class take precedence.</p><p><strong>TODO: May want a more complex
check; what if user uses prop: in the template and there's a
conflict?</strong></p><p>You may override the default component id (as derived
from the field name) using the id() attribute of the Component
annotation.</p><p>If you define a component in the component class, and there
is no corresponding element in the template, Tapestry will log an error. In the
example above that would be the case if the template for the Countdown page
didn't contain an element with <code><t:count
t:id="count"></code>.</p></div>
</div>
<div class="clearer"></div>
