| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Carthago | Army | 87.0 | no sea consetetur tempor |
| Roma | 185.0 | Lorem et labore dolore | |
| Carthago | 583.0 | kasd magna eos et | |
| 667.0 | sanctus takimata labore diam | ||
| Roma | 874.0 | Lorem ea amet Stet | |
| Neapolis | 889.0 | dolores nonumy dolor tempor | |
| Arts | 37.0 | invidunt amet tempor aliquyam | |
| Olympia | 225.0 | At diam diam ea | |
| 698.0 | clita nonumy justo nonumy | ||
| Roma | 824.0 | Stet est vero At |
| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Roma | Army | 1.0 | vero et invidunt duo |
| Carthago | 4.0 | takimata Stet sit magna | |
| Olympia | 209.0 | ut et sit tempor | |
| Carthago | 508.0 | sed sanctus dolore vero | |
| Roma | 772.0 | no justo sed ut | |
| Arts | 44.0 | diam ut nonumy duo | |
| Neapolis | Gladiators | 111.0 | takimata sadipscing et est |
| Carthago | 444.0 | erat duo sit At | |
| Neapolis | 477.0 | dolor clita et dolores | |
| 754.0 | voluptua ipsum et et |
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.