Hi, Please go through this link you will find the source code.This is pretty help ful for drop down.
http://www.wicket-library.com/wicket-examples/ajax/choice.0 On Wed, Apr 29, 2009 at 11:18 AM, PDiefent <pdief...@csc.com> wrote: > > Hi Vladimir, > for the solution, look at > http://www.nabble.com/Update-DropDownChoice-td22944165.html > Peter > > Vladimir K wrote: > > > > PDiefent, > > > > I've came across similar problem. In my case, and what I'm discovered > fits > > your case as well, the following is happening: > > > > ModalWindow is component based. It is rendered in two parts. The first > > part is all you put into your markup. The second part is dynamically > built > > within a separate div within the <body> tag. > > > > Concerning browser's DOM, your form and modal window form are not > > overlapped. Nothing is passed for DDChoice when modal window form is > > submitted. > > Concerning wicket tree your form and modal window form are overlapped > > (modal form is within). So when wicket is updating formcomponent models > > (and it starts from the outermost form for some reason), it has to fill > > DDC, but nothing is passed in request for it. So wicket fills it with > > null, what explains "choose a value" message in it. > > > > I don't know what is actually wrong - how wicket is processing form or > > ModalWindow implementation that renders modal window somewhere outside of > > the place you pointed. It is up to authors to decide. > > > > I'm going to investigate workarounds. Will be back if suceed. > > > > -- > View this message in context: > http://www.nabble.com/Update-DropDownChoice-with-ModalWindow-tp22595072p23290916.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards. Geeta Madhavi. K
