[
https://issues.apache.org/jira/browse/WICKET-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390370#comment-17390370
]
Dirk Forchel commented on WICKET-6910:
--------------------------------------
With Wicket 8.10.0 the exception is not thrown anymore, but an error log
message is shown:
[main] ERROR org.apache.wicket.request.cycle.RequestCycle - Error detaching
RequestCycle
org.apache.wicket.core.request.mapper.StalePageException: A request to page
'[Page class = com.mycompany.StalePageExceptionTest$StalePageExceptionPage, id
= 0, render count = 3]' has been made with stale 'renderCount'. The page will
be re-rendered.
This means, changes made with
[WICKET-6831|https://github.com/apache/wicket/commit/e5cd09ba8c1c02f213b1e47bbe9dff0e626120ea]
(see RequestCycle#handleDetachException) cause the new behavior.
> StalePageException not thrown
> -----------------------------
>
> Key: WICKET-6910
> URL: https://issues.apache.org/jira/browse/WICKET-6910
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 8.10.0
> Reporter: Dirk Forchel
> Assignee: Sven Meier
> Priority: Major
> Attachments: myproject.zip
>
>
> In our wicket application we have a unit test that simulates a
> StalePageException for a RequestCycleListener. This test no longer works as
> expected since version 8.10.0. Prior to this version the test was working.
> This test assumes that the StalePageException is thrown during the rendering
> phase, but this is no longer the case. I'm not sure if this is a bug or if
> the test setup has become wrong.
> I'm also not sure if this issue is related to WICKET-6869.
> Attached you will find a quick start with the StalePageExceptionTest.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
