> > 1) Generifying* Wicket > [x] Should be avoided, I prefer the way 1.3 works. Because... (fill > in your opinion here). > After seeing the impact that generics had on the codebase, I'm begining to feel that it's not worth the effort. Trying to *JUST* generify models seems like a half baked solution which will constantly trigger users asking, "why isn't foo using generics?" My biggest fear is that the API will bloat and become less understandable by adopting generics.
> > 2) How strongly do you feel about your choice above? > [x] Whatever choice ultimately made, I'll happily convert/ start > using 1.4 and up. I trust the wicket core devs 100% so whatever they implement, I'll take a look at. Just remember to Keep It Simple!!! =)
