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 < martin.maku...@koodaripal

Re: Doubt about form components

2010-02-23 Thread Martin Makundi
Hi! I don't see the problem, setDefaultModelObject also clears input via internalOnModelChanged: public final Component setDefaultModelObject(final Object object) { final IModel model = (IModel)getDefaultModel(); // Check whether anything can be se

Re: Doubt about form components

2010-02-23 Thread Pedro Santos
Hi Martin, call get or set defaultModel is not the solution, consider this another test case: The new link implementation: AjaxLink link = new AjaxLink("reload") { @Override public void onClick(AjaxRequestTarget target) { textFie

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 wrote: > Yes.. don't use referenceToModel. Instead call > > textField.getDefaultModelObject(); > > ** > Martin > > 2010/2/23 Pedro Santos : >> Hi Martin, consider this form: >> >> java code: >>        Form form = new Form("f

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 : > Hi Martin, consider this form: > > java code: >        Form form = new Form("form"); >        add(form); >        final TextField textField = new TextField("tf", new > Model());

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 TextField textField = new TextField("tf", new Model()); textField.setType(Integer.class); textField.setOutputMarkupId(true); form.add(textField); AjaxLin