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 on
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
ti
Ok. There are more nested components than necessary, though.
ExecutableRowPair.tml:
ExecutableRowPair.java:
Stack trace (actually the null pointer exception is in ExecutableRowPair):
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Null-pointer-exception-when-updat
I'm try to show a list of components with AJAX zones in a table:
An 'ExecutableRowPair' consists of a header row (that's always visible) and
a details row, that's loaded through AJAX. The request is triggered by an
event link in the header row.
In ExecutablePair.java, I'm injecting the compon
