On Tue, 20 Mar 2012 10:51:05 -0300, trsvax <trs...@gmail.com> wrote:
In my particular case things like Freemarker are not versatile enough. My
first problem is only part of my project is Java so I need something that
does not require Java. For better or worse I can use XSLT in Cobol on a
mainframe. Next I send/receive a lot of data via XML to/from other
systems that do not have Java. Java objects are not my primary data
representation and there may not even be any Java in my data flow.
Nice points. :) Context is everything.
I do have one question. I'm not familiar with Freemarker and I can
understand using it standalone but what advantage does it have over
Tapestry templates that would make it worth learning if you are already
using
Tapestry? When I need that kind of functionality I just call a Tapestry
page like a web service. Then I get my whole environment including
services,
permissions etc.
Tapestry templates are meant to be used in Tapestry pages and components,
so it uses all the Tapestry infrastructure (components, mixins, bindings,
etc). FreeMarker is a generic text template engine. I'd use FreeMarker to
generate e-mails based in a template (unless there's a Tapestry page which
could be also used for generating the e-mails), for example, or for
providing some templating features to be used by the users of a website.
Summary: use Tapestry templates for Tapestry-powered pages and components,
FreeMarker for other templating needs which don't benefit from the
Tapestry infrastructure.
--
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
