Re: Using non-Model fields in Form

2011-02-01 Thread nimmy
I'm a newbie also but Can't you just create a new model specifically for the RadioChoice component? Each component can have its own model. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Using-non-Model-fields-in-Form-tp3251063p3251807.html Sent from the

Re: Using non-Model fields in Form

2011-02-01 Thread msj121
As Nimmy said you should be able to supply your own model to the RadioChoice which will override the CompoundPropertyModel Assuming NUMBERS is a list... RadioChoiceString rc = new RadioChoiceString(numberRadioChoice, new Model(),NUMBERS); Look at

Re: Using non-Model fields in Form

2011-02-01 Thread Pedro Santos
Sure. When you create an radio choice like: RadioChoiceString rc = new RadioChoiceString(numberRadioChoice, NUMBERS); your are passing the wicket id and a list of choices to the component, but no model. Components without model inherit one from the first parent CompoundPropertyModel based on the

Re: Using non-Model fields in Form

2011-02-01 Thread James Carman
This is exactly why I tell folks not to use CPM. People start relying on them too heavily and when all doesn't work as planned, they freak out. It's like the blonde that got locked in her car because the battery died and her automatic locks didn't work. On Tue, Feb 1, 2011 at 10:25 AM, nimmy