Is there a good reason (besides backwards compatiblity) that the objectautocomplete hasn't replaced the broken string based one in wicket-extensions?
It seems like AutoComplete should behave as similarly to DropDownChoice as possible. As it currently is, IChoiceRenderer feels broken with it. -Clint On Tue, Jun 14, 2011 at 9:49 AM, Martin Grigorov <[email protected]>wrote: > maybe you need > https://github.com/wicketstuff/core/tree/master/jdk-1.5-parent/objectautocomplete-parent > > On Tue, Jun 14, 2011 at 5:42 PM, drf <[email protected]> wrote: > > I have a model which backs a form. > > One of the fields in the model is a custom object type, City. > > In the form I have a field defined as AutoCompleteTextField<City>. > > This is populated with a list of City objects, and because > City.toString() > > is overriden, everything displays nicely in the list. > > However, when a city is chosen, the model does not appear to be getting > > updated. I cannot find another way to access the City object which was > > selected. > > Can anyone help? > > > > > > -- > > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/AutoCompleteTextField-which-uses-an-Object-not-a-String-tp3596762p3596762.html > > Sent from the Users forum mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
