In my current project we try to do everything by BookmarkablePageLinks.
Count:
- 1 Link with an abstractreadonlymodel
- 14 Links without model
- 13 bookmarkablepagelinks without model
- 2 ajaxfallbacklinks without model
in addition we have 4 many used subclasses of bookmarkablepagelink that
do not have a model.
Maybe not representative, but with 1 link with a model out of 30+ lead
me to think that Link without generics is just fine. For Forms I would
like to keep generics.
Regards,
Erik.
Igor Vaynberg wrote:
the question here is: do most people use the model in the Link or not?
when you use compound property model in conjunction with form
components you never call getmodel/object() on those either. what now?
not generify form components? i dont think a strict criteria will
work.
some components fall into a gray area which needs to be discussed and
generified on case by case basis. when i was generifying wicket my
primary usecase is to use Link with a model so i went that way. start
a discussion/vote and see where that goes in a different thread. i
will be happy to go with what the majority thinks in this particular
case.
-igor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
