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 :) -- View this message in context: http://tapestry.1045711.n5.nabble.com/Null-pointer-exception-when-updating-a-component-in-a-loop-tp5719424p5719452.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
