This is because using an interface for an ASO requires some additional
configuration of Tapestry. By the end of this chapter, we shall learn how to do such
configuration, but right now, let's just leave everything as it is.
Chapter 4
[ 101 ]
Well, frankly speaking, it is not the best of ideas to provide a data source
as an ASO. Application State Object is normally a convenient place
to store some information, while it would be better if a data source
is maintained as a Tapestry service. However, I find it important to
introduce new ideas gradually, step by step. Custom services will appear
in the last chapter only. So let the data source be an ASO for now. Not the
best design, but it will work.
For this code to work, we need to have a Details page in our application. Please add
such a page??”a template, and an empty page class??”in the same way as we did this
before with every new page.
When an ActionLink component is rendered, it produces an HTML link and
whatever we have provided as a context for this component gets recorded into the
link. For example, if you hover your mouse over the last name of the fifth celebrity in
the list, you should be able to see the following in the status bar of your browser:
http://localhost:8084/celebrities/showall.
Pages:
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141