Author: buildbot
Date: Mon Oct 14 12:20:40 2013
New Revision: 882526
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/component-events-faq.html
websites/production/tapestry/content/component-events.html
websites/production/tapestry/content/implementing-the-hi-lo-guessing-game.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/component-events-faq.html
==============================================================================
--- websites/production/tapestry/content/component-events-faq.html (original)
+++ websites/production/tapestry/content/component-events-faq.html Mon Oct 14
12:20:40 2013
@@ -73,7 +73,7 @@ table.ScrollbarTable td.ScrollbarNextIco
<h3><a shape="rect"
name="ComponentEventsFAQ-WhydoesTapestrysendaredirectafteraformissubmitted%3F"></a>Why
does Tapestry send a redirect after a form is submitted?</h3>
-<p>This is an extension of the <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/Post/Redirect/Get"; >redirect after post</a>
approach. It ensures that after an operation that updates server-side state,
such as a form submission, if the user resubmits the resulting page, the
operation is <b>not</b> performed a second time; instead just the results of
the operation, reflecting the changed server-side state, is re-rendered.</p>
+<p>This is an extension of the <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/Post/Redirect/Get"; >Post/Redirect/Get</a>
approach. It ensures that after an operation that updates server-side state,
such as a form submission, if the user resubmits the resulting page, the
operation is <b>not</b> performed a second time; instead just the results of
the operation, reflecting the changed server-side state, is re-rendered.</p>
<p>This has the unwanted requirement that any data needed to render the
response must persist between the event request (the form submission) and the
render request; this often means that fields must be annotated with @<a
shape="rect" class="external-link"
href="http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Persist.html";>Persist</a>.</p>
Modified: websites/production/tapestry/content/component-events.html
==============================================================================
--- websites/production/tapestry/content/component-events.html (original)
+++ websites/production/tapestry/content/component-events.html Mon Oct 14
12:20:40 2013
@@ -88,11 +88,11 @@
</td></tr><tr><td colspan="1"
rowspan="1">
<span class="icon icon-page"
title="Page">Page:</span>
- <a shape="rect"
href="component-events-faq.html">Component Events FAQ</a>
+ <a shape="rect"
href="component-events.html">Component Events</a>
</td></tr><tr><td colspan="1"
rowspan="1">
<span class="icon icon-page"
title="Page">Page:</span>
- <a shape="rect"
href="component-events.html">Component Events</a>
+ <a shape="rect"
href="component-events-faq.html">Component Events FAQ</a>
</td></tr></table>
</div>
@@ -323,7 +323,7 @@
<p>In the above example, the navigational response is the page itself.</p>
-<p>If there is no exception event handler, or the exception event handler
returns null (or is void), then the exception will be passed to the <a
shape="rect" class="external-link"
href="http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/RequestExceptionHandler.html";>RequestExceptionHandler</a>
service, which (in default configuration) will be render the exception
page.</p>
+<p>If there is no exception event handler, or the exception event handler
returns null (or is void), then the exception will be passed to the <a
shape="rect" class="external-link"
href="http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/RequestExceptionHandler.html";>RequestExceptionHandler</a>
service, which (in the default configuration) will render the exception
page.</p>
</div>
</div>
Modified:
websites/production/tapestry/content/implementing-the-hi-lo-guessing-game.html
==============================================================================
---
websites/production/tapestry/content/implementing-the-hi-lo-guessing-game.html
(original)
+++
websites/production/tapestry/content/implementing-the-hi-lo-guessing-game.html
Mon Oct 14 12:20:40 2013
@@ -174,7 +174,7 @@ public class Index
<p>Note that the event handler method does not have to be public; it can be
protected, private, or package private (as in this example). By convention,
such methods are package private, if for no other reason than it is the minimal
amount of characters to type.</p>
-<p>Hm. Right now you have to trust me that the method got invoked. That's no
good ... what's a quick way to tell for sure? One way would be have the method
throw an exception, but that's a bit ugly.</p>
+<p>Hmm... right now you have to trust me that the method got invoked. That's
no good ... what's a quick way to tell for sure? One way would be have the
method throw an exception, but that's a bit ugly.</p>
<p>How about this: add the @<a shape="rect" class="external-link"
href="http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Log.html";>Log</a>
annotation to the method:</p>
@@ -204,7 +204,7 @@ public class Index
<p>The @Log annotation directs Tapestry to log method entry and exit. You'll
get to see any parameters passed into the method, and any return value from the
method ... as well as any exception thrown from within the method. It's a
powerful debugging tool. This is an example of Tapestry's meta-programming
power, something we'll use quite a bit of in the tutorial.</p>
-<p>Why do we see two requests for one click? Tapestry uses an approach based
on the <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/Post/Redirect/Get"; >Redirect After Post</a>
pattern. In fact, Tapestry performs a redirect after each component event. So
the first request was to process the action, and the second request was to
re-render the Index page. You can see this in the browser, because the URL is
still "/tutorial1" (the URL for rendering the Index page). We'll return to
this in a bit.</p>
+<p>Why do we see two requests for one click? Tapestry uses an approach based
on the <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/Post/Redirect/Get"; >Post/Redirect/Get</a>
pattern. In fact, Tapestry generally performs a redirect after each component
event. So the first request was to process the action, and the second request
was to re-render the Index page. You can see this in the browser, because the
URL is still "/tutorial1" (the URL for rendering the Index page). We'll return
to this in a bit.</p>
<p>We're ready for the next step, which involves tying together the Index and
Guess pages. Index will select a target number for the user to Guess, then
"pass the baton" to the Guess page.</p>
