Mario Ivankovits wrote:
What problems do you have by using nested tables and the suggested
workaround?
Every aliased component need its own backing bean then to ensure
uniqueness.
Your can use a map for this. But how could that be a problem with the
datatable?
Your hack doesn´t work on tables if you alias the row var and use it
for a binding.
Alias the "row var" - what do you mean?
the datatable has a attribute var which is used to get the current
instance for each row while the datatable is iterating the datamodel. If
you bind a component through an alias to that var it wouldn´t work with
your workaround since the datatable doesn´t iterate over the rows when
you process the aliases in the restoreView method of your Viewhandler.
Your alias will be null.
Regards,
Mathias
