Re: DynamicWizards and Forms
Yes but they don't cover the scenario where the new wizard step is submitted even before it is displayed. Investigated this a bit further and it seems that the delegation by the model to the actual wizard step does not happen in the correct order. I'll try and recreate this with a very simple dynamic wizard and work from there. On 2 Apr 2010, at 18:36, Jeremy Thomerson wrote: have you looked at the wizard examples in the wicket-examples package? http://www.wicket-library.com/wicket-examples/ -- Jeremy Thomerson http://www.wickettraining.com On Thu, Apr 1, 2010 at 8:49 AM, Sumit Raja sumitr...@gmail.com wrote: Hello, I am trying to get a dynamic wizard to work with a series of forms. I have the following flow: (1) Select document type - (2) if document type has embedded audio provide an upload form otherwise skip - (3) Document editing form. In next() of step 1 I am creating a new Panel with a form of either upload or of document editing based on doc type. The odd thing is that the submit on the form for step 2/3 seems to get called when next is clicked on (1) but before the step (2 or 3) is displayed. Looking through the code the if appears that the next() method gets called before the actual form processing is performed meaning that the form on the next step gets processed as well as the last step. In delegateSubmit(), formToProcess.visitChildren seems to be the actual place that the next step from gets submitted, before the previous step processing is complete. What is the correct way to structure a Dynamic wizard when each step has nested forms to prevent the visitor submitting the form on the next step as well? Thanks Sumit - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DynamicWizards and Forms
If you can recreate it in a quickstart, you can send it to the list and we can get a better idea of what you mean. -- Jeremy Thomerson http://www.wickettraining.com On Sun, Apr 4, 2010 at 5:41 AM, Sumit Raja sumitr...@gmail.com wrote: Yes but they don't cover the scenario where the new wizard step is submitted even before it is displayed. Investigated this a bit further and it seems that the delegation by the model to the actual wizard step does not happen in the correct order. I'll try and recreate this with a very simple dynamic wizard and work from there. On 2 Apr 2010, at 18:36, Jeremy Thomerson wrote: have you looked at the wizard examples in the wicket-examples package? http://www.wicket-library.com/wicket-examples/ -- Jeremy Thomerson http://www.wickettraining.com On Thu, Apr 1, 2010 at 8:49 AM, Sumit Raja sumitr...@gmail.com wrote: Hello, I am trying to get a dynamic wizard to work with a series of forms. I have the following flow: (1) Select document type - (2) if document type has embedded audio provide an upload form otherwise skip - (3) Document editing form. In next() of step 1 I am creating a new Panel with a form of either upload or of document editing based on doc type. The odd thing is that the submit on the form for step 2/3 seems to get called when next is clicked on (1) but before the step (2 or 3) is displayed. Looking through the code the if appears that the next() method gets called before the actual form processing is performed meaning that the form on the next step gets processed as well as the last step. In delegateSubmit(), formToProcess.visitChildren seems to be the actual place that the next step from gets submitted, before the previous step processing is complete. What is the correct way to structure a Dynamic wizard when each step has nested forms to prevent the visitor submitting the form on the next step as well? Thanks Sumit - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DynamicWizards and Forms
have you looked at the wizard examples in the wicket-examples package? http://www.wicket-library.com/wicket-examples/ -- Jeremy Thomerson http://www.wickettraining.com On Thu, Apr 1, 2010 at 8:49 AM, Sumit Raja sumitr...@gmail.com wrote: Hello, I am trying to get a dynamic wizard to work with a series of forms. I have the following flow: (1) Select document type - (2) if document type has embedded audio provide an upload form otherwise skip - (3) Document editing form. In next() of step 1 I am creating a new Panel with a form of either upload or of document editing based on doc type. The odd thing is that the submit on the form for step 2/3 seems to get called when next is clicked on (1) but before the step (2 or 3) is displayed. Looking through the code the if appears that the next() method gets called before the actual form processing is performed meaning that the form on the next step gets processed as well as the last step. In delegateSubmit(), formToProcess.visitChildren seems to be the actual place that the next step from gets submitted, before the previous step processing is complete. What is the correct way to structure a Dynamic wizard when each step has nested forms to prevent the visitor submitting the form on the next step as well? Thanks Sumit - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
DynamicWizards and Forms
Hello, I am trying to get a dynamic wizard to work with a series of forms. I have the following flow: (1) Select document type - (2) if document type has embedded audio provide an upload form otherwise skip - (3) Document editing form. In next() of step 1 I am creating a new Panel with a form of either upload or of document editing based on doc type. The odd thing is that the submit on the form for step 2/3 seems to get called when next is clicked on (1) but before the step (2 or 3) is displayed. Looking through the code the if appears that the next() method gets called before the actual form processing is performed meaning that the form on the next step gets processed as well as the last step. In delegateSubmit(), formToProcess.visitChildren seems to be the actual place that the next step from gets submitted, before the previous step processing is complete. What is the correct way to structure a Dynamic wizard when each step has nested forms to prevent the visitor submitting the form on the next step as well? Thanks Sumit - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
