1) Generifying* Wicket
[X] Can best be done like currently in the 1.4 branch, where models
and components are both generified. I care most about the improved
static type checking generified models and components give Wicket.
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 haven't tried migrating to 1.4 yet (waiting for the dust to settle),
so I don't have any first-hand experience.
The last java posse podcast discussed the wicket generics problem at
length (though without any direct knowledge of the issues). They
recommended a book for designing generified APIs, but the title
escapes me. Here's the podcast link:
http://media.libsyn.com/media/dickwall/JavaPosse189.mp3
I don't mean to imply that the core devs haven't already mastered all
there is to master about generics, but everyone seems to agree that
they can be tricky little beasts. I don't mind waiting longer for 1.4
if that's what it takes.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
