| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Neapolis | Army | 51.0 | labore vero accusam elitr |
| Carthago | 268.0 | accusam diam consetetur justo | |
| Neapolis | 459.0 | sanctus sea diam sadipscing | |
| Carthago | 479.0 | ut eos accusam At | |
| Olympia | 831.0 | amet nonumy vero justo | |
| 953.0 | et rebum elitr diam | ||
| Arts | 22.0 | consetetur voluptua takimata erat | |
| Carthago | 319.0 | clita dolores diam erat | |
| 417.0 | clita rebum voluptua tempor | ||
| Roma | 698.0 | invidunt clita takimata Stet |
| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Roma | Army | 152.0 | Lorem no ea dolor |
| Neapolis | 322.0 | elitr nonumy accusam vero | |
| Carthago | 747.0 | consetetur nonumy amet labore | |
| Olympia | 900.0 | invidunt justo sanctus ut | |
| Neapolis | Arts | 524.0 | voluptua dolor sanctus labore |
| 954.0 | sed sed sed dolores | ||
| Gladiators | 193.0 | ipsum diam et diam | |
| Roma | 763.0 | diam kasd tempor invidunt | |
| Olympia | 799.0 | vero diam amet ut | |
| Carthago | 863.0 | erat Lorem takimata ut |
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.