If somebody still interested in solution... The problem lies here:
//Grid.getSortConstraints()
PropertyModel sortModel = getDataModel().getById(sortColumnId)
exception is raised because sort order is updated when the grid data model
is still null (strangely enough, it is not null at the first
Hi Szemere,
you are right, I also thought about this. But the result is a bit
confusing:
1. the nice little arrows don't show which column is sorted initially
(because Grid doesn't know about the sort order)
2. if the user figures out that the Grid is sorted by, say, the "Code"
column, an
Hi! I've had similar issue.
My grid had custom model, and I've uses @Persist on it instead of @Retain.
And page refresh issue was solved.
Christoph Jäger wrote:
>
> It works on 5.0.15 the first time a page is displayed. For the second
> time (just clicking the same link in my menu), I get a
I've got to say, I prefer the low-tech way of just sorting the collection
before I give it to the Tapestry grid - it's a lot simpler than the above.
This doesn't explain why you have the above issue, but it does give you a
workaround.
Szemere
