Now, find all the references to the MockDataSource ASO (there should be two of
them, at the ShowAll and Details pages) and replace the MockDataSource type
with IDataSource. That's it. Now, as soon as you request for the ASO, Tapestry
will check its configuration to see whether there is a creator for the requested
IDataSource type. We have just provided one, and so it will be used to do the job
(and generate an instance of MockDataSource behind the scenes). I hope this isn't
difficult to understand.
Summary
We have learned a lot in this chapter:
We are now closely familiar with a number of Tapestry components??”
TextField, PasswordField, Label, PageLink, ActionLink, Loop, If,
Output, RadioGroup and Radio, Checkbox, Submit and Select. This
knowledge is not just theoretical as we used all these components in a web
application and saw how they work.
We now have a good understanding of how form submission works. We
have plenty of flexibility in defining which code and when it should run in
the process of submission.
We have explored how to implement a master-detail-like pattern in two
different ways??”with ActionLink and PageLink components.
???
???
???
Simple Components
[ 126 ]
We have created a good foundation for the future Celebrity Collector web
application.
Pages:
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172