Hi Thanks for the link. Would have to use a repeater to support more generic
ones. Thanks
niv
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/PageableListView-to-work-with-Set-tp3064909p3068641.html
Sent from the Users forum mailing list archive at Nabble.com.
So I gather from your response that I should use a list type object only.
Since PageableListView uses it for indexing,sorting etc. Am I right then to
convert either the entity to use a List or on the front end to map from a
Set into a List.
Thanks for the time
Niv
--
View this message in
Hi.
See Java Doc for PageableListView
http://wicket.apache.org/apidocs/1.4/org/apache/wicket/markup/html/list/PageableListView.html
and it's ascendant
http://wicket.apache.org/apidocs/1.4/org/apache/wicket/markup/html/list/ListView.html.
From Java Doc:
A ListView is a repeater that makes it
I guess it expects only a List type object. I can work around this by
converting the Set into a List and then provide it but felt somehow this is
a limitation. How can I work with generic collections?
Any thoughts much appreciated
No, because ordering requires the indexing a List has. In
