svn commit: r891494 - in /websites/production/tapestry/content: cache/main.pageCache using-beaneditform-to-create-user-forms.html
Author: buildbot
Date: Sun Dec 22 21:20:43 2013
New Revision: 891494
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/using-beaneditform-to-create-user-forms.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==
Binary files - no diff available.
Modified:
websites/production/tapestry/content/using-beaneditform-to-create-user-forms.html
==
---
websites/production/tapestry/content/using-beaneditform-to-create-user-forms.html
(original)
+++
websites/production/tapestry/content/using-beaneditform-to-create-user-forms.html
Sun Dec 22 21:20:43 2013
@@ -29,6 +29,7 @@
+
SyntaxHighlighter.defaults['toolbar'] = false;
SyntaxHighlighter.all();
@@ -77,19 +78,8 @@ table.ScrollbarTable td.ScrollbarParent
table.ScrollbarTable td.ScrollbarNextName {text-align: right;border: none;}
table.ScrollbarTable td.ScrollbarNextIcon {text-align: center;width:
16px;border: none;}
-/*]]>*/
https://cwiki.apache.org/confluence/images/icons/back_16.gif"; width="16"
height="16">Implementing the Hi-Lo
Guessing Game https://cwiki.apache.org/confluence/images/icons/up_16.gif"; width="8"
height="8">Tapestry
Tutorial Using Tapestry With
Hibernate https://cwiki.apache.org/confluence/images/icons/forwd_16.gif"; width="16"
height="16">
-
-In the previous chapters, we saw how Tapestry can handle simple links, even
links that pass information in the URL. In this chapter, we'll see how Tapestry
can do the same, and quite a bit more, for HTML forms.
-
-Form support in Tapestry is deep and rich, more than can be covered in a
single chapter. However, we can show the basics, including some very common
development patterns. To get started, let's create a simple address book
application.
-
-We'll start with the entity data, a simple object to store the information
we'll need. These classes go in an entities sub-package. Unlike
the use of the pages sub-package (for page component classes),
this is not enforced by Tapestry; it's just a convention (but as we'll see
shortly, a handy one).
-
-Tapestry treats public fields as if they were JavaBeans properties; since
the Address object is just "dumb data", there's no need to get carried away
writing getters and setters. Instead, we'll define an entity that is all public
fields:
-
-src/main/java/com/example/tutorial/entities/Address.java
-