On Wed, 25 Apr 2012 06:10:47 -0300, Lance Java <lance.j...@googlemail.com>
wrote:
Please stop saying that there is a bug in tapestry or that tapestry is
forcing bad design on you.
Thiago has pointed out that he often uses a single page for create and
edit.
This grid issue seems to have nothing to do with that. Of course you
need a
property to store the current row in a grid. That is the tapestry way.
And it seems that you're reusing the same field for the grid's current row
*and* the object being edited or created. This is probably the cause of
your problems. Have two separate fields, one for each scenario (listing or
editing).
--
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
