This content has been marked as final. Show 4 replies
Yeah, I can see why it's doing that, the bindings are all being evaluated at the same time so there is no iteration over the table values yet. Do you have to use bindings? It might be simpler to just use the value= attribute and ensure the backing bean has getters and setters for a suitable table, and it might also work with the nested table.
I have to use binding inorder to add columns at runtime to the innerTable based on outerRowData
I tried having a backing bean property for the inner table as below:
return innerTableGui =( (OuterTableRowData)getOuterTableGui().getRowData()).getInnerTableGui();
problem is it is getting called onlyonce..and the first row data is applied to all other rows.