I don't see how this is not a Tapestry issue. My code is pretty simple. Neither ajaxformloop nor loop sync values, for rows added after the form has rendered, back to the server. All rows created during execution of the loop are synced. I'm using tapestry 5.2.6.
On Thu, Jul 14, 2011 at 10:57 AM, Mark <mark-li...@xeric.net> wrote: > On Thu, Jul 14, 2011 at 8:16 AM, Ray Nicholus <rnicho...@widen.com> wrote: > > It turns out that my encoder is not the problem. In fact, this appears > to > > be an issue with Tapestry. I was not using the id from Hibernate and I > > verified beforehand that my encoder was properly coded. I had a couple > > other people look into this as well, and it appears that Tapestry is not > > able to sync values to the server for form elements added via ajax (after > > the render cycle has completed) unless the page is reloaded. > > I'd be pretty surprised if this is the general case. I know this is > being used a lot in different places. I think you can even find > examples of it in the Jumpstart tutorials: > > > http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/ajaxformloop1 > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
