[
https://issues.apache.org/jira/browse/WICKET-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552169#comment-13552169
]
vineet semwal commented on WICKET-4792:
---------------------------------------
there is still a bug in this method in my opinion,my apology for responding
late,i didn't use this method in long time and i do it mechanically what this
method does when there is a need...
ok here is the problem ,since this method doesn't do/go_through a normal
processRequestAndDetach() ,i think it's good to do a component#detach() in
the end in this method else problems can be the component's requestFlags will
get cached and so the behavior will not be expected foreg. on next
tester#startcomponent(component) ,the component's configure() and
beforerender() won't work as expected ie. onconfigure() and onbeforerender()
won't be called..
thanks :)
> 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
