[
https://issues.apache.org/jira/browse/WICKET-7143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921386#comment-17921386
]
Pedro Santos commented on WICKET-7143:
--------------------------------------
Failing test case demonstrating the issue:
https://github.com/pedrosans/wicket/tree/WICKET-7143-failing-test
> StatelessLink has different lifecycles depending on whether it was added to
> the page inside the constructor or #onInitialize method
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-7143
> URL: https://issues.apache.org/jira/browse/WICKET-7143
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 10.4.0
> Reporter: Pedro Santos
> Priority: Major
>
> When resolving a component with the listener interface for the request,
> inside a stateless page, PageAndComponentProvider#getComponent tries to:
> * get the component from a fresh page instance, if not found:
> * get the component from the page after invoking Page#internalInitialize and
> Page#beforeRenderer
> So depending on whether the component was added to the page inside the
> constructor or not, the Component#onConfigure method will be invoked before
> the listener interface once a link is clicked on a stateless page.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
