[
https://issues.apache.org/jira/browse/WICKET-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390422#comment-17390422
]
Dirk Forchel commented on WICKET-6910:
--------------------------------------
Okay, I undertand.
??No, this is not how it works: with setExposeException(false) Wicket's default
exception handling should kick in, e.g. rerendering the page after
StalePageException.??
I know that Wicket's default exception handling should occur when
setExposeException(false). Therefore, the unit test asserts that the same page
is rendered afterwards with a redirect. I thought that throwing the
StalePageException was expected behavior, which is why I tested this too.
By the way, I think the naming of setExposeException is a bit confusing, at
least to me.
Thank you for your comments and your help.
Please close this issue.
> 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
> Fix For: 8.14
>
> 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)
