You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2012/10/03 14:00:07 UTC

[jira] [Resolved] (WICKET-4792) wickettester#startcomponent(component) doesn't call oninitialize

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

Martin Grigorov resolved WICKET-4792.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.9
                   6.2.0
         Assignee: Martin Grigorov
    
> wickettester#startcomponent(component) doesn't call oninitialize
> ----------------------------------------------------------------
>
>                 Key: WICKET-4792
>                 URL: https://issues.apache.org/jira/browse/WICKET-4792
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.8, 6.0.0
>            Reporter: vineet semwal
>            Assignee: Martin Grigorov
>             Fix For: 6.2.0, 1.5.9
>
>
> currently wicketester#startcomponent(component) only executes beforerender which causes onbeforerender to be executed however onInitialize() is missed out .
> beforerender+internalinitialize will be a good behavior..
> thanks !

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira