This produces a nicer and shorter logical name and URL, while the
page files still retain the original name we have given to them.
Do not be surprised when, after creating a page called, UserRegistration and
placing it into the \user subdirectory, you will have to use the logical name user/
registration, while the page class will still be named UserRegistration.
By the way, do you still remember that Tapestry is case-insensitive when
it comes to the names of components and pages? But not the names of
classes in Java code!
Chapter 3
[ 73 ]
Since we are already speaking about users, it can be mentioned that quite often
we shall want to have some information available for all the pages of our web
application, and a typical example of such information is user specific settings,
preferences and other details. It would be a burden to pass all this information
between pages; we would rather prefer to have it available at any time whenever
we need to look up one or another detail. Let's see how we can achieve this in a
Tapestry application.
Creating and Using an Application State
Object
In Tapestry, an object that is made available for every page of the application is
termed Application State Object (ASO).
Pages:
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105