Brill Pappin wrote:
Why can't this be done the way the java API does it, and allow people to use it or not as they want? Wicket is pretty clean in terms of the API, and there are interfaces for most things... So what's the problem with adding the generics to the interfaces?AFAIK this would allow them to be ignored if the user didn't have a place for them.
Well for one, getHomePage() does not compile if you returned home page is not generified, so it's not really that simple (opt in vs opt out).
Regards, Sebastiaan
- Brill Pappin-----Original Message-----From: Jan Kriesten [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2008 11:46 AMTo: [email protected] Subject: Re: users, please give us your opinion: what is your take on generics with Wicket Hi Sebastiaan,I *really* would like to see a clarification of this statement. In Wicket the component and model are very tightly coupled.that's part of the problem, agreed.What is a *gooddesign* alternative, where only IModel is generified? getModelObject() returns Object? getModel returns IModel<?>?IMHO the practical solution would be to leave generics from components and have getModelObject return Object, yes. On certain components (ListView e.g.), those methods may be overridden by more concrete implementations. Regards, --- Jan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
