Re: Doubt about form components

2010-02-23 Thread Pedro Santos
Hi Martin, consider this form: java code: Form form = new Form(form); add(form); final TextFieldInteger textField = new TextField(tf, new Model()); textField.setType(Integer.class); textField.setOutputMarkupId(true); form.add(textField);

Re: Doubt about form components

2010-02-23 Thread Martin Makundi
Yes.. don't use referenceToModel. Instead call textField.getDefaultModelObject(); ** Martin 2010/2/23 Pedro Santos pedros...@gmail.com: Hi Martin, consider this form: java code:        Form form = new Form(form);        add(form);        final TextFieldInteger textField = new

Re: Doubt about form components

2010-02-23 Thread James Carman
Or, call modelChanged()? On Tue, Feb 23, 2010 at 7:06 AM, Martin Makundi martin.maku...@koodaripalvelut.com wrote: Yes.. don't use referenceToModel. Instead call textField.getDefaultModelObject(); ** Martin 2010/2/23 Pedro Santos pedros...@gmail.com: Hi Martin, consider this form: java

Re: Doubt about form components

2010-02-23 Thread Pedro Santos
In the step 3, the user isn't changing the model value, so setDefaultModelObject don't call internalOnModelChanged. The user intent that can be update the component markup will fail, unless he call modelChanged by his own. On Tue, Feb 23, 2010 at 9:59 AM, Martin Makundi