| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Roma | Arts | 729.0 | sadipscing nonumy eirmod Lorem |
| Carthago | 780.0 | accusam sed labore no | |
| 789.0 | Lorem et rebum est | ||
| 906.0 | tempor aliquyam sea et | ||
| Olympia | Gladiators | 255.0 | et sed et aliquyam |
| Neapolis | Taxes | 406.0 | ea dolores sed rebum |
| Olympia | 445.0 | kasd dolores et kasd | |
| Neapolis | 561.0 | magna amet ea sanctus | |
| Carthago | 882.0 | elitr eirmod labore takimata | |
| 893.0 | justo Stet et takimata |
| CITY | PROJECT | HOURS | TASK |
|---|---|---|---|
| Carthago | Army | 111.0 | dolor eirmod At duo |
| Neapolis | 309.0 | Lorem eirmod sit eos | |
| Roma | 437.0 | sadipscing diam tempor sed | |
| Neapolis | 815.0 | dolor magna et consetetur | |
| 822.0 | et kasd sit eos | ||
| 962.0 | dolor et rebum voluptua | ||
| Roma | Arts | 122.0 | no ut voluptua Lorem |
| Olympia | 341.0 | ipsum duo eirmod sed | |
| Carthago | 383.0 | sit invidunt voluptua vero | |
| 456.0 | et eos diam ipsum |
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.