I think its not quite that simple. Certainly both sets of components should use generics (silly to have a partial solution) but how its done is vital so that it doesn't become a huge mess.
I'm one of the adopters of the M1 release and I've found it quite difficult to keep things straight sometimes. - Model objects should allow any generic needed (due tot he nature of a model). - Components should be specific about the generics they accept i.e. instance of model etc. makeing the generics clean will help us keep our code clean. - Brill Pappin Eelco Hillenius wrote: > > We have had several threads in this and the dev list, and some > discussions in the public on how to incorporate generics in Wicket. > > I'd like to use this thread to gather the opinions of as many regular > Wicket users as we can. Please help us get an impression of what our > users think about the issue by completing this simple survey. Note > that it is not a vote; we only want to get an idea of what you think. > -- View this message in context: http://www.nabble.com/users%2C-please-give-us-your-opinion%3A-what-is-your-take-on-generics-with-Wicket-tp17589984p17602906.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
