> Having multiple models is rare, however, having one model that can > (but doesn't have to) be used is more common imho.
Not that rare if I look at my code, especially if you take panels and fragments into account. I have plenty of places where I use two or three models. > Wicket is kinda optimized for the later, so if you don't use the model there > is no > runtime cost associated. If we didn't have "default" model slot this > would be more difficult to achieve. The problem with generics now is that the model isn't as optional anymore. So you'd have to use void or whatever. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
