Hi Igor,
igor.vaynberg wrote: > > yes it sucks. i agree. personally i prefer code written against wicket > 1.3. even in 1.3 i hardly had to cast anything and even with those > casts i do not remember getting any class cast exceptions. > It is nice to know that somebody thinks similar to me :) The generics in Wicket looks nice on examples. But in bigger application (we have aprox. 500k loc) it is a mess. Especially when we use lots of forms, models, adapters and so on. We must write more code than in 1.3 and we do not get any reward for it ;) I'm thinking now whether cancel migration and stay with wicket 1.3 or add this all voids and questions marks (thanks Stefan!) and get used to it. How long do you want to support (bug fixing, adding small improvements to 1.3) and when do you plan do release 1.5 :) Thanks in advance for your advices. Artur -- View this message in context: http://www.nabble.com/Migration-to-1.4---generic-headache-tp20205449p20222475.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]
