Igor Vaynberg wrote:
i dont know of any examples like that.what it entails is something like this wrappermodel extends model { private IModel delegate; [ ... ]
Yeah, that sounds like a lot of work, but maybe I'm missing something.
or you can do the inverse, implement your own IChoiceRenderer which might actually be simpler. the choice renderer can do the opposite of what the model does.
This is what I was trying as your previous message came in. And it gets me past the original error. My test case doesn't actually do anything on submit, and I started thinking that it won't do any good to change the renderer, because I still have the issue of a String property on my POJO and an Item in the dropdown.
I'm going to have to think this through some more. Thank you very much for your amazingly quick and helpful responses. -- Scott ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
