> Oh, and type-safe models are a must, I was surprised to read in this > thread not everybody agrees with that. Especially since type erasure > ensures backwards compatibility, and lets the cast-fans stick to their > habits :-)
The problem that I have with type safe models is that in order to fit them into Wicket, we have to make components make typed as well. And that's not always a good fit, and makes the code a lot more verbose, not just a little bit (at least with Java's current state of inference). Anyway, I'm not against it really... some aspects of it just annoy me :-) Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
