You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2010/02/13 17:04:28 UTC

[jira] Resolved: (WICKET-2740) DynamicWizardModel: setActiveStep is called twice

     [ https://issues.apache.org/jira/browse/WICKET-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Donnerstag resolved WICKET-2740.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-M1
                   1.4.7
         Assignee: Juergen Donnerstag

> DynamicWizardModel: setActiveStep is called twice
> -------------------------------------------------
>
>                 Key: WICKET-2740
>                 URL: https://issues.apache.org/jira/browse/WICKET-2740
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.3.4
>            Reporter: Vincent MATHON
>            Assignee: Juergen Donnerstag
>             Fix For: 1.4.7, 1.5-M1
>
>
> DynamicWizardModel constructor calls setActiveStep(startStep);  Thus, the Initial step onInit method is called where as the form is not already created. When calling Wizard init() method, there is a call to DynamicWizardModel reset() method  that leads to a second Initial step onInit method call. This time, the form is created but I have exceptions since I have already added the components of my first step on the first call to onInit.
> Removing the call to setActiveStep(startStep); in the DynamicWizardModel constructor solves the bug (note that the activeStep is correctly initialized by the reset method call).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.