I've debugged a simple example and what I described before happens to
the letter, both for ajax updating behavior and for
wantOnSelectionChangedNotifications/onSelectionChanged. I don't think
it's a bug at all, but imo it would be reasonable to clear out the
input if the explicit intention of changing the formcomponent value
(through the model object in this case) is there. Anyway, maybe this
is not related to JulianS' problem.
Do you want the example?
Regards,
Carlos
On 9/7/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> does it work properly without ajax?
>
> -igor
>
>
> On 9/6/07, JulianS <[EMAIL PROTECTED]> wrote:
> >
> >
> > I am using Wicket 1.2.6. I have 3 DropDownChoices (and some other fields)
> > on
> > a form.
> >
> > The first DropDownChoice resets the selections in the other
> > DropDownChoices
> > using AjaxFormComponentUpdatingBehavior("onchange"). All the
> > DropDownChoices
> > use PropertyModels.
> >
> > This all works fine until the form is submitted and validation fails. In
> > this (normal) situation the form is still visible, with the feedback
> > messages displayed, but the 2nd and 3rd DropDownChoices no longer react to
> > the first DropDownChoice. I have verified that the properties on which
> > DropDownChoices depend are being correctly set.
> >
> > Is there anything I can do to make them behave properly? Any help is
> > appreciated.
> >
> > Thanks,
> > Julian
> >
> > --
> > View this message in context:
> > http://www.nabble.com/Problem-with-DropDownChoice-and-AjaxFormComponentUpdatingBehavior-tf4394596.html#a12531138
> > 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]
