On Wed, 10 Feb 2010 18:46:50 -0200, Alfonso Quiroga
<alfonsose...@gmail.com> wrote:
Thanks Thiago, always fast and clear. So clear that I will ask something
(maybe basic) I don't get.
They say wicket is better in the component model, they talk about
"dynamic component model" where tapestry is static. What does it mean?
This is really basic stuff about Tapestry.
It means that the component tree (the pages and the components it uses the
the components useds by the components and then recursively) is static.
This allows Tapestry to pool pages instances and the session is not used
to store the state of page renders. Thus, Tapestry can perform faster and
use way less memory per user than Wicket.
I paste here the answer I got from a user, I hate wicket urls, and he
answered this:
---
“Ugly URLs” because stateful pages are session relative.
Exactly what I said above (Wicket stores page render state in the session,
Tapestry doesn't). Tapestry has stateful pages (@Persist) without
polluting the URL (unless you're using client persistence strategy).
And yes, there are
easy ways to customize this, including from Wicket. T5 creates friendly
URLs by default, but at the cost of things that Wicket provides and T5
doesn’t
(like a dynamic component model,
Most situations don't need a dynamic component model. In the other ones
that need it, with a little bit of imagination and with some tricks in
mind you can overcome that. Just see what BeanEditForm and BeanEditor do:
they create forms, using Tapestry components, dynamically, on-the-fly.
stateful pojo programming model,
Wicket isn't really POJO because pages and components must extend some
class (public class HelloWorld extends WebPage {...}). This doesn't happen
in Tapestry, which actually has a stateful POJO programming model.
security by default, etc).
I don't know what he's talking about here.
Wicket is a nice framework and, AFAIK, the most similar to Tapestry. Your
friend is not correct about some things he/she said.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, 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
