On Thu, 28 Apr 2011 18:03:09 -0300, Pierce T. Wetter III
<pie...@twinforces.com> wrote:
I think we're saying the same thing in different ways.
"Tapestry compiles the template into a program to generate the content"
is a shorter way of saying what you just said. As opposed to JSP which
interprets the template character by character.
Other systems (WebObjects is one) convert templates into data
structures, but I think Tapestry is unique in the way that it builds
property accessors into those structures. To me that smacks much more of
compilation than interpretation.
<pedantic>
IMHO, both scenarios (templates into objects and property accessors) are
not compilation because they doesn't involve translating from one language
into another. Tapestry does a lot of bytecode generation, but this also
isn't compilation.
</pedantic>
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
