On Thu, 13 May 2010 09:58:15 -0300, Christian Riedel
<cr.ml...@googlemail.com> wrote:
Why should you have the same rendering code in two different components?
When I have common code for several components I create an abstract base
component and put it into the base package. The template is not
mandatory for components or abstract base components/pages btw. You can
use subclassing whenever you want but that doesn't always makes your
code better.
Exactly. I was saying that components provided by Tapestry aren't meant to
be subclassed, but the ones you write can be. Tapestry's components use
subclassing too: AbstractField, AbstractTextField, etc. Maybe Tapestry
should have some more of them, just like an AbstractSelect.
If you have common logic in different components you should move it into
a service...
Nice advice. :)
Well, and I think tapestry can't free you from your dirtyness, you
should try soap :)
No, thank you. :P
--
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
