Not sure why you would want the double redirect ..... but here goes.
Use either Swarm, Auth-roles or a custom security implementation to
redirect you to a login page. After sign-in use setResponsePage to
redirect the user to your other page. In that page you can then return
the user to the original page by calling
continueToOriginalDestination() followed by a return in the
constructor. However keep in mind that there is not always an original
destination (see return value of continueToOriginalDestination()).
The above is just as easily accomplished with just one intercept. By
using this little construct in your sign-in page after signing in.
if (!getPage().continueToOriginalDestination())
{
setResponsePage(WhatEverPage.class); //or new WhatEverPage(complex
constructor);
}
Maurice
On 10/19/07, Cristi Manole <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I was wondering if the following use case can be implemented in wicket:
>
> -> a page requires authentification (@AuthorizeInstantiation())
> -> if it's not authentif, it will be intercepted by a SignIn.class
> -> based on a rule, i want to send the user to another page.
> -> that page will redirect the user to the original page.
>
> How could I accomplish this?
>
> Thanks in advance.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
