In addition to all this FormFragment and Zone components have their own
implementation of FormSupport service that renders separate t:formdata
hidden inputs. But to use this functionality on zone you should return
whole Zone instead of just its body in event handler.
Object onUpdate() {
return updateZone;
}
So, you have a possibility to change/delete all stored process submissions
for components placed inside this zone.
On Thu, Sep 27, 2012 at 12:08 PM, Michael Wyraz
<[email protected]>wrote:
> Hi,
>
> yesterday I discussed with a colleague the possibility of replacing T5
> form components (parts of a form) with ajax zone updates.
> The basic problem is:
> - each component registers itself as "process submission" to the form (via
> formsupport)
> - the form serializes all those submissions to a hidden field "t:formdata"
> - during submit the submissions are deserialized and executed
> So it it not possible to change the submissions without replacing the
> whole form. There are some workarounds that allows to add new form field by
> emulating formsupport and add extra t:formdata fields to the form.
>
> Yesterday we had an idea for a different approach which I'd like to
> discuss here. What if each form field would render it's own submission to
> it's own t:formdata field? In this case it would not require formsupport to
> register itself to the form. The field would still be handled by the form
> during submission. But the component itself could then simply be added or
> removed with ajax.
>
> Regards,
> Michael,
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> dev-unsubscribe@tapestry.**apache.org<[email protected]>
> For additional commands, e-mail: [email protected]
>
>
--
BR
Ivan
