=getSet().iterator();
for (int i=0;i -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Nathan Hamblen
> Sent: Thursday, October 27, 2005 7:30 AM
> To: wicket-user@lists.sourceforge.net
> Subject: [Wicket-user] Re: replace ogn
I think it would be very practical to both keep such a OGNL property
model /and/ see how we can support both that and our improved property
model in compound property models.
Eelco
On 10/27/05, Nathan Hamblen <[EMAIL PROTECTED]> wrote:
> I use ognl {} projection to make non-List Collections into
Nathan Hamblen wrote:
I use ognl {} projection to make non-List Collections into Lists for a
ListView. (And it /is/ way too slow with long lists.) If list view could
handle a SortedSet, or just any Collection, it would eliminate that need.
I created my own List Component in a few minutes that
I use ognl {} projection to make non-List Collections into Lists for a
ListView. (And it /is/ way too slow with long lists.) If list view could
handle a SortedSet, or just any Collection, it would eliminate that need.
It would still be nice to have an OgnlPropertyModel, even if it doesn't
have
