Author: buildbot
Date: Mon Oct 14 19:20:44 2013
New Revision: 882584
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/confluence-site-setup.html
websites/production/tapestry/content/default-parameter.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/confluence-site-setup.html
==============================================================================
--- websites/production/tapestry/content/confluence-site-setup.html (original)
+++ websites/production/tapestry/content/confluence-site-setup.html Mon Oct 14
19:20:44 2013
@@ -106,7 +106,7 @@
<p><em>For more details see the <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/tapestry/tapestry-site/trunk/README";>SiteExporter
README</a>.</em></p>
-<p>SiteExporter is a command-line Java program that is run hourly (currently
at 20 minutes after the hour) from Apache's BuildBot. It makes a web service
call to Confluence (to its RSS feed, actually) to get a list of each page that
has changed since the last run, and the HTML-formatted export of those pages.
For each, it post-processes the file (described below). Finally, SiteExporter
commits all changed HTML files into Tapestry's part of the Apache Subversion
repository, which (nearly instantly) makes it available to the public at <a
shape="rect" class="external-link"
href="http://tapestry.apache.org";>http://tapestry.apache.org</a>, and commit
emails are sent to Tapestry's "commits" mailing list.</p>
+<p>SiteExporter is a command-line Java program that is run hourly (currently
at 20 minutes after the hour) from Apache's BuildBot. It makes a web service
call to Confluence (to its RSS feed, actually) to get a list of pages that have
changed since the last run, and the HTML-formatted export of those pages. For
each, it post-processes the file (described below). Finally, SiteExporter
commits all changed HTML files into Tapestry's part of the Apache Subversion
repository, which (nearly instantly) makes it available to the public at <a
shape="rect" class="external-link"
href="http://tapestry.apache.org";>http://tapestry.apache.org</a>, and commit
emails are sent to Tapestry's "commits" mailing list.</p>
<p>Attachments (to Confluence pages) are exported in roughly the same way.</p>
Modified: websites/production/tapestry/content/default-parameter.html
==============================================================================
--- websites/production/tapestry/content/default-parameter.html (original)
+++ websites/production/tapestry/content/default-parameter.html Mon Oct 14
19:20:44 2013
@@ -91,11 +91,11 @@ table.ScrollbarTable td.ScrollbarNextIco
</td></tr><tr><td colspan="1"
rowspan="1">
<span class="icon icon-page"
title="Page">Page:</span>
- <a shape="rect" href="default-parameter.html">Default
Parameter</a>
+ <a shape="rect"
href="component-parameters.html">Component Parameters</a>
</td></tr><tr><td colspan="1"
rowspan="1">
<span class="icon icon-page"
title="Page">Page:</span>
- <a shape="rect"
href="component-parameters.html">Component Parameters</a>
+ <a shape="rect" href="default-parameter.html">Default
Parameter</a>
</td></tr></table>
</div>
@@ -129,9 +129,9 @@ public class RichTextEditor implements F
]]></script>
</div></div>
-<p>Every component has a unique id; if you don't assign one with the
<tt>t:id</tt> attribute, Tapestry will assign a less meaningful one. Component
ids can end up inside URLs or used as query parameter names, so using
meaningful ids helps if you are ever stuck debugging a request. The most common
case of using autoconnect is form control components such as TextField and
friends ... or this RichTextEditor.</p>
+<p>Every component has a unique id; if you don't assign one with the
<tt>t:id</tt> attribute, Tapestry will assign a less meaningful one. Component
ids can end up inside URLs or used as query parameter names, so using
meaningful ids helps if you are ever stuck debugging a request.</p>
-<p>This repetition can be avoided by adding the autoconnect attribute to the
@Parameter annotation:</p>
+<p>This repetition can be avoided by adding the <em>autoconnect</em> attribute
to the @Parameter annotation:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
@@ -141,9 +141,11 @@ public class RichTextEditor implements F
]]></script>
</div></div>
-<p>This can now be written as <tt><t:richtexteditor
t:id="profile"/></tt>. The unwanted repetition is gone: we set the id of the
component and the property it edits in a single pass. </p>
+<p>This can now be written as <tt><t:richtexteditor
t:id="profile"/></tt>. The unwanted repetition is gone: we set the id of the
component and the property it edits in a single pass.</p>
+
+<p>If there is no matching property, then a runtime exception will be thrown
when loading the page because the value parameter is required and not bound.</p>
-<p>If there is no matching property, then a runtime exception will be thrown
when loading the page because the value parameter is required and not
bound.</p></div>
+<p>The most common case of using autoconnect is form control components such
as TextField and friends ... or this RichTextEditor.</p></div>
</div>
<div class="clearer"></div>
