Nested tables
| Id |
Status |
Comments |
Related address |
| 50803 |
TEMPOR |
aliquyam ipsum... |
| Name |
Email |
| sed |
duo@eirmod.com |
| eirmod |
Stet@diam.com |
| amet |
sanctus@sadipscing.com | |
| 7315 |
ET |
sit et... |
| Name |
Email |
| sed |
sea@sea.com |
| vero |
accusam@At.com |
| et |
vero@ea.com | |
| 47433 |
IPSUM |
sed sanctus... |
| Name |
Email |
| voluptua |
ut@et.com |
| takimata |
ipsum@ipsum.com |
| est |
dolor@eirmod.com | |
| 17845 |
SANCTUS |
rebum est... |
| Name |
Email |
| sea |
accusam@Lorem.com |
| no |
sea@invidunt.com |
| et |
voluptua@vero.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?).