| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Olympia | Army | 281.0 | ea sanctus elitr voluptua |
| Neapolis | Army | 590.0 | sit At ea kasd |
| Carthago | Arts | 291.0 | voluptua et Lorem aliquyam |
| Neapolis | Arts | 295.0 | sed tempor duo kasd |
| Olympia | Arts | 562.0 | sanctus kasd ut duo |
| Neapolis | Arts | 726.0 | ea dolores rebum justo |
| Carthago | Arts | 764.0 | diam diam sea Stet |
| Neapolis | Arts | 841.0 | et duo et voluptua |
| 858.0 | et ipsum sadipscing gubergren | ||
| Roma | Arts | 973.0 | sanctus gubergren justo amet |
| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Neapolis | Army | 561.0 | eos dolore ut et |
| Roma | Army | 638.0 | sed accusam erat takimata |
| 808.0 | sanctus duo eos vero | ||
| Neapolis | Arts | 302.0 | vero et labore et |
| 310.0 | voluptua sadipscing et no | ||
| Carthago | Gladiators | 155.0 | et sed elitr sea |
| Neapolis | Gladiators | 333.0 | rebum Lorem eirmod et |
| Roma | Gladiators | 350.0 | magna Stet tempor kasd |
| Neapolis | Taxes | 392.0 | et vero sea At |
| 535.0 | diam labore diam sanctus |
Do you need to put more than one <display:table> in the same page, with independent
pagination and sorting?
No problem: parameter in pagination, sorting and exporting are encoded to be processed only by the source table.
The only requirement is to provide a different id attribute for the table. If you click on sorting or
pagination links in one of the previous tables the other one doesn't get affected by that.