[
https://issues.apache.org/jira/browse/WICKET-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588398#comment-13588398
]
Martin Grigorov commented on WICKET-5023:
-----------------------------------------
I've added try/catch for the #isPageStateless() check in 6.x branch.
If this is useful for you I can downport it to 1.5.x.
> Page store process is broken if an exception occurs at commit request phase.
> ----------------------------------------------------------------------------
>
> Key: WICKET-5023
> URL: https://issues.apache.org/jira/browse/WICKET-5023
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.9, 6.5.0
> Environment: ubuntu 12.10
> jdk 1.6.0_30
> Reporter: Anton
> Attachments: brokenPageStoringTestCase.zip
>
>
> Wicket generates non-working links on custom error page if an exception
> occurs at commit request phase. Click on any link causes PageExpiredException.
> This happens because page is not stored during request processing.
> Steps to reproduce:
> - Add RequestCycleListener handling all exceptions and redirecting to custom
> error page (see. WicketApplication.init)
> - Add security check (see. WicketApplication.init). This example contains
> simplified security check.
> - Create error page (ErrorPage)
> - Create login page (LoginPage)
> - Create secured page (HomePage) containing:
> -- Point 5. A component causing an exception at render phase
> -- Point 6. Another component causing an exception at stateless check
> - Start application. LoginPage appears.
> - LoginPage: Click "Login". ErrorPage appears.
> - ErrorPage: Click "Back to Main". PageExpiredException occurs and ErrorPage
> appears again.
> see attached test case.
--
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