Thanks a lot, Thiago! Yes, passing the child as a context parameter fixes it.
In ExecutableRowPair.java: I think Tapestry does try to figure out the component parameters for a partial update, but for loops, it can't. In the loop, the same instance of 'ExecutableRowPair' is rendered multiple times with different parameters. Thus the component injected by is always the same and doesn't hold the information for a particular iteration. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Null-pointer-exception-when-updating-a-component-in-a-loop-tp5719424p5719437.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
