| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Roma | Army | 45.0 | amet consetetur ut diam |
| Olympia | 81.0 | justo kasd est kasd | |
| Neapolis | 125.0 | dolore rebum dolore At | |
| Roma | 171.0 | diam et invidunt ipsum | |
| Carthago | 343.0 | invidunt dolores ipsum voluptua | |
| Roma | 587.0 | amet At sit et | |
| Olympia | 671.0 | Stet amet et accusam | |
| Carthago | Arts | 15.0 | sit rebum duo justo |
| Olympia | 345.0 | ipsum invidunt takimata eirmod | |
| Carthago | 464.0 | no diam sed tempor |
| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Carthago | Army | 111.0 | dolor eirmod At duo |
| Arts | 383.0 | sit invidunt voluptua vero | |
| 456.0 | et eos diam ipsum | ||
| Gladiators | 447.0 | ipsum sea sadipscing diam | |
| Neapolis | Army | 309.0 | Lorem eirmod sit eos |
| 815.0 | dolor magna et consetetur | ||
| 822.0 | et kasd sit eos | ||
| 962.0 | dolor et rebum voluptua | ||
| Taxes | 771.0 | clita At sit sed | |
| Olympia | Arts | 341.0 | ipsum duo eirmod sed |
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.