The weird behaviour is the following:
eash subclass declaration in a tml-file results in 2 rendered fields in
output - at first Tapestry renders subclass instance, which is
correct, but after this it also renders the parent instance too, which is
not needed.
----- Original Message -----
From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Friday, April 15, 2011 2:54 PM
Subject: Re: extending Select component
On Fri, 15 Apr 2011 07:18:14 -0300, Keio Kraaner <k.kraa...@gmail.com>
wrote:
And what about the weird behaviour which results when rendering a child
of a Tapestry component?
Which weird behaviour?
Any way, Tapestry-provided components are not meant to be subclassed. It
is recommended to create mixins when possible.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
