Hi, Just to answer... your answer: the ACTF can work either with String type or beans. Sure, the user enters a String but the ACTF is using the internal converter (the class type should have been provided in the ctor) to retrieve the bean reference back (from the previous choice list).
About your use case, I think Igor's wicket-select2 is the best choice... Best regards, Sebastien. On Tue, Apr 16, 2013 at 7:16 PM, heikki <tropic...@gmail.com> wrote: > thanks for your replies, > > @Igor : trying it, however when loading the page I get: "TypeError: > $(...).select2 is not a function". Can you give some instruction as how to > wire things together? From the wicket-select2-examples, it is not obvious > to > me where any JS gets included. > > @Sebastien: sure, a validator can refuse input (doesn't even need to be a > String I guess?), but that is also too late (after you already put in a > free > text value and submitted). I'm looking for a way to prevent unwanted input > client-side; the validator will be there as last resort server-side. > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/How-to-force-user-to-select-from-AutoComplete-choices-tp4658033p4658041.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
