On Sun, 11 Sep 2011 10:25:35 -0300, Wechsung, Wulf <wulf.wechs...@sap.com>
wrote:
For one, components are basically singletons so you can never have the
same component twice on the page. You can have it render twice with
different parameters which can accomplish the same thing but makes it
necessary to careful manage the components state.
This is not true at all. Pages are singletons, but components aren't. Any
time you write <t:xxx> or <div t:type="xxx"> in a template, it's a
completely different instance from any other.
What I do think is a real problem is the lack of recursion in
components. It's not possible to have a component contain itself even
indirectly.
As far as I know, you can use indirectly (A has B which uses A), but not
directly (A uses B). Recursion can be avoided in almost all cases and in
the remaining ones you can achieve recursion by rendering HTML through
MarkupWriter and component rendering events instead. Tapestry 5.3 has a
Tree component.
--
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
