I used some of your stuff but ran into a suspected 1.3.3 Wicket bug (see previous message I just sent out).
Thanks for the help - go and enjoy your weekend. Michael -----Original Message----- From: Doug Donohoe [mailto:[EMAIL PROTECTED] Sent: Friday, May 09, 2008 6:41 PM To: [email protected] Subject: RE: DropDownChoice throws IllegalArgumentException with Integer values You can get at the underlying Integer by calling getKey() on the IntegerSelectChoice object the model holds. If that doesn't work, you'll have to figure out an alternative on your own. The good news is that you have working code to start from. -Doug Michael Mehrle wrote: > > I like your solution, but you are using an IntegerSelectChoice as your > model, which won't work for me. I need to set my model to a regular > Integer since that's what's being persisted on the backend. > > Michael > -- View this message in context: http://www.nabble.com/DropDownChoice-throws-IllegalArgumentException-wit h-Integer-values-tp17139227p17159082.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
