Hi Ernesto,
On Tue, May 28, 2013 at 10:51 AM, Ernesto Reinaldo Barreiro < [email protected]> wrote: > Hi, > > > On Tue, May 28, 2013 at 11:46 AM, Martin Grigorov <[email protected] > >wrote: > > > On Tue, May 28, 2013 at 10:41 AM, Martin Makundi < > > [email protected]> wrote: > > > > > > You could not use normal form processing, I guess, as there will not > be > > > any > > > > form components at server side... (they will be removed after list is > > > > displayed). So, you will have to do some ticks to map cliente state > > with > > > > server state. > > > > > > > > The examples above could be make to work for non read-only > > situations... > > > > but maybe not using wicket default form processing machinery... > > > > > > Feels like reinventing the wheel at both serverside and html ;) > > > > > > > @Martin, > > Sometimes when wheels at hand are not good enough for a certain terrain you > should ask yourself if it it not easier to invent a new one. > > > > > > You can try to do this in > > > > org.apache.wicket.markup.html.form.Form#process(IFormSubmitter) { > > > > rebuild(); > > > > super.process(formSubmitter); > > > >} > > > > > > Ok. Will try something along these lines. > > > > > > > You will need to call #inputChanged() to all FormComponents in your > > ListView, because this method is called earlier than > > Form#process(IFormSubmitter). > > > > > @Marting, > > Wouldn't list view be "empty" at this point? As all components where > removed at the end of previous request cycle? > Martin Makundi wants to rebuild the ListView items when the form is submitted. I.e. the form components will be created and then the form processing will proceed. > > Best, > > Ernesto >
