Ok, then is the content found at these two pages not relevant for v1.4? http://cwiki.apache.org/WICKET/nested-forms.html and http://cwiki.apache.org/WICKET/conditional-validation.html
I understand the idea of nested forms and I understand that HTML only supports one form. I had hoped that Wicket would only process the submitted form versus the entire form (whole form is submitted, only nested form actually processed). And from the content on the pages, I had thought it was a more common use case. My intent was to have a main form with various fields and then a grouping of fields within a nested form. This nested form was supposed to be submitted using an AjaxSumitLink for the nsted form. I suppose an alternative would be to have a custom behavior that called serializeForm on the client and then handled the component processing on its own. The trick in that case would be the FormValidators. If you have a better idea, I'm all ears. Thanks for the input. On Fri, Feb 19, 2010 at 1:56 PM, Igor Vaynberg <igor.vaynb...@gmail.com>wrote: > you cannot have an "isolated embedded form", as far as html is > concerned that is an oxymoron. you can try hacking around it with > IFormVisitorParticipant or by overriding form.process() on your main > form, etc. but i do not think this is a usecase we will support... > > -igor > > > On Fri, Feb 19, 2010 at 10:09 AM, Charles Deal <chuckdea...@gmail.com> > wrote: > > I'm sorry to bump this. At the least, can anyone point me to some code > that > > has successfully implemented isolated, nested forms using Wicket 1.4.x? > > > > > > On Wed, Feb 17, 2010 at 8:43 AM, Charles Deal < > charles.d...@missionse.com>wrote: > > > >> I am attempting to put an isolated form within the main form of my page. > I > >> found http://cwiki.apache.org/WICKET/nested-forms.html which was > helpful > >> in understanding how the processing works. I was even more excited when > I > >> found http://cwiki.apache.org/WICKET/conditional-validation.html which > >> instructed me exactly how to alter the form object to do what I wanted. > >> Unfortunately, the trick does not work as I expected it to. > >> > >> It seems that if I simply implement > >> IFormVisitorParticipant.processChildren, it is not enough to stop the > Nested > >> form's FormValidator from firing when the main form is submitted. > >> Therefore, I tried to implement the isEnabled technique. This did have > the > >> desired effect the first time through a page (enter data, submit main, > no > >> nested validator fires) but when the page re-renders after the submit, > the > >> nested form is now disabled! It seems that the findSubmittingButton() > >> method finds the button that was used to submit the form, even though > the > >> page is rendering again. > >> > >> Another thing I noticed upon my different attempts is that altering the > >> isEnabled method to use findSubmittingButton() won't work because > >> findSubmittingButton() calls isEnabled()! which puts the code in an > infinite > >> loop. > >> > >> Could someone please enlighten me on how to code an isolated nested form > >> using Wicket 1.4.x. Where isolated means that I want the form to have > its > >> own submit button and those fields are only > submitted/processed/validated > >> when that button is clicked. I want the form to be ignored by the > parent > >> form. > >> > >> > >> ________________________________ > >> This is a PRIVATE message. If you are not the intended recipient, please > >> delete without copying and kindly advise us by e-mail of the mistake in > >> delivery. > >> NOTE: Regardless of content, this e-mail shall not operate to bind MSE > to > >> any order or other contract unless pursuant to explicit written > agreement or > >> government initiative expressly permitting the use of e-mail for such > >> purpose. > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
