[jira] [Commented] (WICKET-6110) Add a message to StalePageException for better debugging

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175905#comment-15175905 ] 

ASF subversion and git services commented on WICKET-6110:
---------------------------------------------------------

Commit 30615aa6a5870da3b666ea8989845371b1abad52 in wicket's branch refs/heads/wicket-6.x from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=30615aa ]

WICKET-6110 Add a message to StalePageException for better debugging


> Add a message to StalePageException for better debugging
> --------------------------------------------------------
>
>                 Key: WICKET-6110
>                 URL: https://issues.apache.org/jira/browse/WICKET-6110
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 7.2.0, 6.22.0
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>            Priority: Minor
>
> At the moment StalePageException doesn't call 'super("Some message")' and also doesn't fill its stack trace (this is intentional!) and when logged it appears in the log as:
> {code}
> Exception occurred:
> org.apache.wicket.core.request.mapper.StalePageException: null
> {code}
> which is not very informative.
> It would be better to set a message that provides some information about the page, like page.toString().



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)