Yea... come to think of it... the generic type gets erased at runtime.
Eelco Hillenius wrote: > > I don't think it is. Limitation of how generics work I'm afraid. > > Eelco > > On 3/20/07, Patrick Angeles <[EMAIL PROTECTED]> wrote: >> >> >> Johan Compagner wrote: >> > >> > no i am not pro for degenerifying it. >> > I like the getModelObject() >> > >> > and that we have to do this: >> > TextField<Integer> integerTextField = new >> > TextField<Integer>(this,"integerProperty", Integer.class); >> > >> >> I haven't looked at Wicket 2.0 source, so I may be off here, but it's >> possible to skip the last parameter of the TextField constructor so it >> looks >> like this: >> >> TextField<Integer> integerTextField = new >> TextField<Integer>(this,"integerProperty") ; >> >> >> -- >> View this message in context: >> http://www.nabble.com/generics-in-Wicket-tf3360271.html#a9580850 >> Sent from the Wicket - Dev mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/generics-in-Wicket-tf3360271.html#a9581986 Sent from the Wicket - Dev mailing list archive at Nabble.com.
