On Wed, 23 Jan 2013 06:03:33 -0200, Peter Farkas <pfark...@gmail.com>
wrote:
Thanks a lot, Thiago! Yes, passing the child as a context parameter
fixes it.
;)
I think Tapestry does try to figure out the component parameters for a
partial update, but for loops, it can't.
I'm sorry, but you're wrong here. It has absolutely nothing to do with
loops. Nothing. The issue, as I've said before, was not passing a
parameter in an later AJAX render. The first render, a full page one,
passed the parameter correctly. A second one, AJAX, didn't. That's why the
addition of the object in the context fixes your code. Loop is a component
like any other in Tapestry, not having any special treatment.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
