The down side of this approach (depending on your target user) is that many users will expect all changes to all Persons to be submitted in a single submit.
You could render a list of Person "views", with each view in a Zone, and then have an Edit Person link that would update the Zone content with an edit Form. If you go with this approach, a place to be careful is the assignment of id's for the zones (not the t:id's), and making sure they agree with the zone parameter on the action links. On Sun, Aug 7, 2011 at 10:27 AM, dkeenan <david_siedle...@yahoo.co.uk>wrote: > Yesss!. Tapestry seems to take care of it if I just create a loop. So I can > loop through each person, create a form for each, and have one Form > component with one set of field props in the page class that each generated > HTML for can submit too. Brilliant. > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/How-do-I-add-a-dynamic-number-of-forms-to-a-page-tp4674893p4675090.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Jonathan Barker ITStrategic
