Yep, as on the tap5devwiki; basically, I'll be serializing into the form, as a single hidden field, a list of commands used to process the form submission. So instead of re-rendering the form to find all the fields and their names (query parameter names, etc.), Tapestry will be able to randomly access the necessary components to make them do their thing. Much cleaner and more efficient. Still a lot of tricky state management issues, especially w.r.t. Ajax style partial updates and other changes.
On 10/26/06, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
On 10/26/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > However, I'm much more interested in the short term in fleshing out things > enough to support forms and other bits of basic functionality. I can see you're wiping out hte rewind phase... right? Ciao -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
