Maybe that's because tapestry keeps track of the sorting in the session and
doing an updateSort reverses the sorting with each page call.
I have this solved as such:
if (grid.getSortModel().getSortConstraints().isEmpty()) {
while
(!grid.getSortModel().getColumnSort("creation_date").equals(ColumnSort.DESCENDING))
{
grid.getSortModel().updateSort("creation_date");
}
}
This will sort enough times to make sure it is descending on each page.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Grid-display-after-a-new-row-insertion-tp4715298p4722399.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
