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 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 an accompanying compound model. Sometimes a complicated expression
> is just what you need, and I'm not crazy about putting those in a
> component ID anyway. But if you're looking to eliminate the ognl jar
> dependency, I guess that's a worthy cause.
>
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
