[jira] [Resolved] (WICKET-4013) Page Class in PageExpiredException

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-4013.
-------------------------------------

    Resolution: Won't Fix

There is no sense in that.
PageExpiredException works only with the page's id which is part of the exception message in trunk.
WICKET-4014 may cover that by implementing a new IRequestMapper which acts as HybridUCS from 1.4.

> Page Class in PageExpiredException
> ----------------------------------
>
>                 Key: WICKET-4013
>                 URL: https://issues.apache.org/jira/browse/WICKET-4013
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.5-RC7
>            Reporter: bernard
>
> We need to recover the page class from PageExpiredException.
> Something like PageExpiredException#getPageClass() and PageExpiredException#getPageParameters().
> In principle, the page class is recoverable from the page URL if the page is mounted. This is easily achievable in Wicket 1.4. In Wicket 1.5, there are some complications, but these are not the subject of this Jira issue.
> Even if the page class is not recoverable in all cases, and PageParameters are yet more difficult to obtain, the concept of maintaining fields in PageExpiredException would clarify and help drive these basic issues towards resolution.
> That is because the required information about the failing page lookup i.e. the path is most likely available exactly where this exception is thrown.
> In other words, a PageExpiredException without the key information of what actually expired is not very helpful.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira