"User" should be a reference to an object that has a field called UserDesignation (bad naming, see below). If you are using 1.3 or newer, this can be private. You can also declare a setter, but the capitalisation will most likely confuse you and Wicket. The choice of identifier names is in fact more than confusing (the capitalisation is wrong, an 'is' prefix usually suggests 'boolean'ness ...), which doesn't help you solve this problem. Worse, it conflicts with the JavaBeans naming conventions expected by the PropertyModel.
User should be user UserDesignation should be userDesignation isUserDesignation should preferably be something like userDesignations etc ... Regards - Cemal http://jWeekend.co.uk http://jWeekend.co.uk mabel25 wrote: > > Hi, > > i have the following codes for a dropdownchoice component. > > > List<String> isUserGender = Arrays.asList("M","F"); > gender = new DropDownChoice("gender", new > PropertyModel(User,"UserGender"), isUserGender); > > List<String> isUserDesignation = Arrays.asList("Operator","Custom > officer", "Warehouse Supervisor", "Top Management"); > designa = new DropDownChoice ("design", new PropertyModel > (User,"UserDesignation"), isUserDesignation); > > > However, i encounterd the following error: > > WicketMessage: unable to set object Top Management > Root cause: > > wicket.WicketRuntimeException: no set method defined for value: Top > Management on object: > > This error disappear after I ran the application a few times but it comes > back again after several tries. > > Anyone knows how to solve this? thanks > > -- View this message in context: http://www.nabble.com/unable-to-set-object-for-dropdownchoice-tp18355243p18525156.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
