Any concrete proposals? Eelco
Igor Vaynberg wrote:
You can provide an interface AND easily support collections because it is very easy to wrap them. The constructor that takes a List interface can wrap that into the internal interface, we shouldn't have to do this the other way around. There is also an impedence mismatch with using lists, webapps cannot depend on the index of an object in a list to identify the object. ListView uses the index to identity an element by default and you have to override it to make it use the pk. I think this is a very bad practice as this is not an obvious problem. Tapestry interfaces provide a reverse lookup method. Igor
------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
