I have a similar problem in that the behavior of SortableDataProvider differs
between systems it's running on. Deploy the same war to dev or test system
and pagination works but in production it doesn't - go figure.
I find that when pagination works there are two calls to size() before the
Could you provide the code for your SortableUserDataProvider, please?
Greg Dunn-3 wrote:
My debugging indicates my
SortableDataProvider is always getting a 0 for the 'first' parameter.
Any ideas why this would happen?
--
View this message in context:
PROTECTED]
Sent: Thursday, March 20, 2008 10:14 AM
To: users@wicket.apache.org
Subject: Re: DefaultDataTable not paging correctly
Could you provide the code for your SortableUserDataProvider, please?
Greg Dunn-3 wrote:
My debugging indicates my
SortableDataProvider is always getting a 0
In the constructor that takes the company id in SortableUserDataProvider, you
are retrieving all users for the specified company id and assigning that to
the users class-level variable. But, in the iterator() method, you
retrieve another subset (page) of users and assign it to the same users
-
From: KennyS [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 10:52 AM
To: users@wicket.apache.org
Subject: RE: DefaultDataTable not paging correctly
In the constructor that takes the company id in
SortableUserDataProvider, you
are retrieving all users for the specified company id
I would not perform an in-memory sort of the entire collection you are
attempting to page, as in your example. One benefit of paging is not having
to return the entire dataset from the backend. If your company has hundreds
or thousands of users, this will become a performance issue.
In the
