don't worry. i believe that reason will prevail. i too am against a /complete/ degenerification, as are all the core developers. we just want to lighten it up some without losing much. in the case of typed textfields, there might be a workaround that doesn't force Component to be parameterized. for example, maybe just TextField<T> is enough. or maybe a typesafe accessor can provide what you want in an IntegerTextField subclass. in any case, i think exactly how and where to degenerify things for whatever comes after 1.3 needs to be discussed at length and there should be plenty of time to talk reasonably.
can you provide more details of generics benefits you don't want to lose? Stefan Lindner wrote: > > I am completely against degenerifying components. We have build a high > abstraction framework with typed components that are reused in several > other components and the generics help us to ensure to use the the use of > the right component at the right place. > Besides some minor problems with suns generic implementation I think that > generic are the most usefull thing for us in Java 5. Type checking at > development time hels to speed up development a lot. > things like > > Integer i = (Integer)integerTextField.getModelObject(); > > always leads to problems at runtime whent the customer suddenly needs a > Dobule field insteda of an Integer field. > And over and above this would be another API break. > > Stefan Lindner > > -- View this message in context: http://www.nabble.com/generics-in-Wicket-tf3360271.html#a9354095 Sent from the Wicket - Dev mailing list archive at Nabble.com.
