The discussion that follows isn't going to be a boring theory, as we are going to learn
the concepts while playing with a Tapestry application, the foundation for which we
have created in this chapter.
???
???
???
The Foundations of Tapestry
In this chapter we are going to learn the following concepts:
A Tapestry application is a set of interactive pages maintained and managed
by the framework.
Each page consists of a page template, which is an XML document, and a
page class, which is a POJO (Plain Old Java Object, meaning that it doesn't
have to inherit from other classes or implement any interface).
A Tapestry page can contain extensions and components. We are going to
learn almost everything about extensions and introduce a few components,
leaving a proper discussion of components for the next two chapters.
It is important to understand in rough detail the life cycle of a Tapestry page,
and how components on a page in a user's web browser are connected to the
properties of the page class.
We can easily navigate from one page to another in a Tapestry application,
and there are a few ways how we can do that.
Tapestry applications can be easily structured according to our needs, and
we are going to find out how to keep pages in order by putting them into
different subdirectories.
Pages:
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70