You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ivan Vasilev (JIRA)" <ji...@apache.org> on 2011/01/16 19:17:44 UTC

[jira] Updated: (WICKET-3340) Custom error 404 page and page id-s

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

Ivan Vasilev updated WICKET-3340:
---------------------------------

    Attachment: quickstart.rar

> Custom error 404 page and page id-s
> -----------------------------------
>
>                 Key: WICKET-3340
>                 URL: https://issues.apache.org/jira/browse/WICKET-3340
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-M3
>         Environment: Windows 7, Chrome 9, Firefox 3.6
>            Reporter: Ivan Vasilev
>         Attachments: quickstart.rar
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1. 
> The example can be found in the attached quickstart. Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.