theigl opened a new pull request, #526: URL: https://github.com/apache/wicket/pull/526
ListenerRequestHandler currently forces initialization of pages. For already initialized stateful pages, this traverses the entire component hierarchy. For large pages, this can be a costly operation. Forcing page initialization was originally introduced in [WICKET-4116](https://issues.apache.org/jira/browse/WICKET-4116) in [this commit](https://github.com/apache/wicket/commit/42a436235ff4ed60f1eaa0f406ea96aa63a6eb2e) to fix an issue with expired pages and checking for statelessness. In [WICKET-5083](https://issues.apache.org/jira/browse/WICKET-5083), [this commit](https://github.com/apache/wicket/commit/34f43642195058f375d161dbb7cec58b40711423) added the same initialization directly to `Page.isPageStateless()`, but invokes it only when necessary. I think we can get rid of the initialization in `ListenerRequestHandler` and rely on the conditional logic in `Page.isPageStateless ()`to trigger initialization if necessary. See https://issues.apache.org/jira/browse/WICKET-6982. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
