Any web application needs to remember many things about the current user
and his or her choices. We are going to have a look at how an application's
state is managed by Tapestry.
Quite a substantial plan for one chapter, but I hope you will enjoy going through it
step-by-step. Let's begin.
??? ???
???
???
??? ???
???
The Foundations of Tapestry
[ 48 ]
Tapestry Application is a Set of
Interactive Pages
It is natural for a user of a web application to think of it as a set of pages. The user
might click on a button, select a value in a drop-down list or do something else, and
the page would display different data, or even a completely different page might be
shown by the application as a result of user actions.
The design of Tapestry is very close to this natural paradigm, as a Tapestry
application actually consists of a number of Tapestry pages.
A Tapestry page is quite a clever entity. It remembers the values entered by the user,
and if the user initiates some action, like clicking on a link or clicking on a button, the
page will react to that action by running an appropriate fragment of code??”an event
handler method. It is for us developers to decide what kind of code it will be and
how it will use the input provided by the user.
Pages:
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71