On Tue, 26 Jul 2011 10:31:28 -0300, dragan.sahpas...@gmail.com
<dragan.sahpas...@gmail.com> wrote:
Yes sure I agree, but I guess It cannot be done inside the BeanEditForm
unless you introduce a new component quite similar to it with this delete
functionality.
Again, just use Form and BeanEditor instead of BeanEditForm. As Taha said,
copy and paste reuse is the worst one by far. In this scenario, it's even
worse, as all the logic BeanEditForm has to generates the fields is
actually imiplemented inside BeanEditor. And Tapestry already has the
building blocks to do almost everything of what the original poster wants.
--
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
