[jira] Updated: (WICKET-1006) Mount vs setPageExpiredErrorPage

["Frank Bille Jensen (JIRA)" <ji...@apache.org>]

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

Frank Bille Jensen updated WICKET-1006:
---------------------------------------

    Fix Version/s:     (was: 1.3.0-rc1)

> Mount vs setPageExpiredErrorPage
> --------------------------------
>
>                 Key: WICKET-1006
>                 URL: https://issues.apache.org/jira/browse/WICKET-1006
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>         Environment: n/a
>            Reporter: Jan Kriesten
>            Priority: Minor
>
> I have the following simple scenario:
> app.mount( new IndexedParamUrlCodingStrategy( "login", LoginPage.class ) );
> app.getApplicationSettings().setPageExpiredErrorPage( LoginPage.class );
> If I call the application, I get directed to the url
> http://appurl/login
> fine. When the Session times out, I get redirected to the LoginPage again, but
> this time not to the above url but to
> http://appurl/?wicket:interface=:2::::
> Couldn't the PageExpiredErrorPage be checked for Mounts?

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