View source
Id Status Comments Related address
8538 REBUM vero et...
Name Email
labore invidunt@et.com
nonumy et@sea.com
diam Lorem@et.com
51040 ET voluptua erat...
Name Email
sed labore@magna.com
ea gubergren@diam.com
takimata sit@diam.com
88240 EST nonumy elitr...
Name Email
ipsum dolores@duo.com
invidunt Stet@dolores.com
voluptua tempor@sed.com
23261 IPSUM et diam...
Name Email
ea accusam@erat.com
amet sed@consetetur.com
dolores et@sea.com

In this sample you can see two nested <display:table>. Table tags can be nested to create sublist, but you need to consider some limitations:

  • You can't use page attributes created by the parent table for iteration in the nested table (for example if you have a parent table with id="parent" you can't use name="pageScope.parent" as source for the nested table). The expression is not evaluated during iteration, but only at the end of the whole table (to avoid useless work when you only need to display a part of the list), so you will get "nothing found to display" as a result, since the object created during page iteration is removed before the display. However, you can use objects created by the parent table do compose an expression like in the current sample.
  • You can use the row index to get the object to display from the parent table list like in the current sample only if you are not using sorting at the same time. If you use sorting the result will be wrong, since the original list is not affected by sorting.
  • Nested tables are not exported (how could you describe nested tables in csv or excel?).