[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-user
Subject:    Re: [5.4-beta-22] Adding forms to a form using ajax
From:       Geoff Callender <geoff.callender.jumpstart () gmail ! com>
Date:       2014-12-19 0:32:52
Message-ID: A0BF8FFA-4DB8-495E-B1D8-A113D619764E () gmail ! com
[Download RAW message or body]

On 18 Dec 2014, at 11:02 pm, Thiago H de Paula Figueiredo <thiagohp@gmail.com> wrote:

> On Thu, 18 Dec 2014 01:21:03 -0200, Geoff Callender \
> <geoff.callender.jumpstart@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.

I should have known that. Thanks Thiago!

Experimenting with a project today, I've also learned that each FormFragment also has \
a formdata field, and its value changes depending on its "visible" parameter. Makes \
sense, since that parameter affects its actions.

Thiago, what I now don't understand is why is a Form's formdata different every time \
it is rendered? A FormFragment's formdata is the same every time, but a Form's \
formdata is not. Is that something to do with the hmac protection?

> 
> > 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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]