In fact, in Tapestry you cannot just mix code and HTML since all Java
code goes into the page class.
In fact, many solutions that are promoted as advanced features of ASP.NET can
be found either in the core Tapestry framework or in a library of custom Tapestry
components, such as Tacos.
It may well happen that with time, as more people realize the benefits of
Tapestry, it might become the model for the next generation of a Java web
framework specification.
However, nothing is perfect, and Tapestry has its downsides too. One of them is
the fact that the framework's development goes ahead in huge steps, which makes
the next version very different from the previous one. To fully appreciate what this
means, let's have a look at a brief history of Tapestry.
The Journey of Tapestry from 3 to 5
Tapestry was originally conceived by Howard Lewis Ship around the year 1999, but
the early versions of the framework are not widely known.
Introduction to Tapestry
[ 14 ]
Tapestry 3 became the first well known version, and I used it for my first Tapestry
application that I created in the summer of 2005. Tapestry was a great relief after my
experience with servlets and JavaServer Pages. Its approach was very easy for me
to understand, maybe because in the past I had plenty of experience with Borland
Delphi, a very popular Rapid Application Development environment.
Pages:
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38