On Tue, 9 Aug 2005 20:12:51 -0700, Igor Vaynberg <[EMAIL PROTECTED]>
wrote:
This wont work unless you override equals in your impl of IModel
IMO that's not true. If I do not override equals/hashCode on the impl of
IModel than there will be just no 'optimized item removal'. DataView will
work this or the other way.
On the other hand currently the user will always have to override
primaryKey() on IDataProvider and has no easy way to turn 'optimzed item
removal' on or off may be even on a per IModel basis.
I also think having primaryKey() is also semantically not realy sound. It
is only important wheter a currently bound model is equal to a fresh
gotten model, wheter this is based on a primaryKey or anything else is
completely implementation specific to the IModel impl (who should know
better?).
Finally I also think that three methods are very often enough on an
interface.
Thanks for checking in the changes and of course for providing the
DataView over all.
Christian
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user