On Thu, 18 Dec 2014 01:21:03 -0200, Geoff Callender
<geoff.callender.jumpst...@gmail.com> wrote:
The starting point of the problem is that Form has a copy of its
rendered state in a hidden field, and it depends on Form knowing what it
rendered.
I'm afraid you got this wrong, Geoff. Tapestry never stores the rendering
of anything like JSF does, for example. Form does store information inside
the t:formdata hidden field, but it's not the rendered state. Instead,
it's instances of ComponentAction created by the form field component
instances in order to process the form submission when it happens.
If you put a Zone inside a Form and you refresh the Zone, and the Zone
contains input fields (any descendant of Field) then you will usually
get an Exception. It's usually a misleading message (something about
Form inside a Form IIIRC), but the reason it cannot be allowed is that
you're not also refreshing Form's hidden state field.
I believe this part is 100% correct.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
