On Wed, 23 Jan 2013 13:54:58 -0200, Peter Farkas <pfark...@gmail.com>
wrote:
Thiago H de Paula Figueiredo wrote
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.
Thank you very much for the clarification. I'm glad it's that simple :)
:) It's simple, as you said, but the two renders, one full, another
partial (AJAX), makes it a little more complicated to understand and to
get it right.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
