PARTS:
Part 1
Part 2
Part 3
Part 4
Part 5
Part 6
Part 7
Part 8
Part 9
Part 10
Part 11
Part 12
Part 13
Part 14
Part 15
Part 16
Part 17
Part 18
Part 19
Part 20
Alexander Kolesnikov
"Tapestry 5: Building Web Applications"
Then, depending on the logic of the application and
the contents of user input, this information is passed either to the original
Tapestry page, or to some other page to handle the submission and generate an
appropriate response.
But what is this mysterious Tapestry page that lives on the server and what does it
look like?
Chapter 3
[ 49 ]
Page Template and Page Class
One of the most discussed problems of web development, and perhaps of software
development in general, is how to separate presentation (what is being shown to
the user) from business logic (what happens behind the scenes). In Tapestry, this
separation is achieved cleanly and easily as every Tapestry page has a template and
a page class.
A page template is an XML document??”something quite similar to a basic XHTML
or an HTML file but written to strict XML rules, and with a few elements not
available in XHTML. As you already know from the previous chapter, Tapestry
page templates have a .tml extension (which is for Tapestry Markup Language). A
Template must be a well-formed XML document, which means that every element
must be either declared as empty or properly closed (say, you can havesrc=""/> or ![]()
, but not just ![]()
), and all attributes'
values must be enclosed in quotation marks.
Pages:
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73
the contents of user input, this information is passed either to the original
Tapestry page, or to some other page to handle the submission and generate an
appropriate response.
But what is this mysterious Tapestry page that lives on the server and what does it
look like?
Chapter 3
[ 49 ]
Page Template and Page Class
One of the most discussed problems of web development, and perhaps of software
development in general, is how to separate presentation (what is being shown to
the user) from business logic (what happens behind the scenes). In Tapestry, this
separation is achieved cleanly and easily as every Tapestry page has a template and
a page class.
A page template is an XML document??”something quite similar to a basic XHTML
or an HTML file but written to strict XML rules, and with a few elements not
available in XHTML. As you already know from the previous chapter, Tapestry
page templates have a .tml extension (which is for Tapestry Markup Language). A
Template must be a well-formed XML document, which means that every element
must be either declared as empty or properly closed (say, you can have
values must be enclosed in quotation marks.
Pages:
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73