Re: DropDownChoice with a different choice class than model class

Yeah, I already had a renderer that was taking care of the conversion for me, it’s just I was subclassing DropDownChoice whose generics are only 1 type (both choices and model value). I ended up subclassing AbstractChoice and copying methods (and modifying them to support model values and choices

Re: DropDownChoice with a different choice class than model class

Hi, for Wicket's choice components the model object type (possibly wrapped in a collection) and the type for each choice has to be identical. That is intended. >In my case, the model object may be a string, but my choices >and renderer are rendering from a complex class. You have two

DropDownChoice with a different choice class than model class

Am I wrong to assume that DropDownChoice (and a few of it’s superclasses) should be using the generic of that AbstractChoice defines where T is the class of the model object and E is the class of choice object? It seems that from AbstractSingleSelectChoice up, it assumes that the value