Indeed, it was what I was searching for. The answer have probably seems too
simple for what I was wanting!
Thanks a lot Erik, it was a matter of copy/pasting to make it work and sorry
because I didn't understand you. Also a big thanks for the explanation from
Igor since it is what made me under
this is exactly what continueToOriginalDestination() coupled with
RestartResponseAtInterceptPage exceptions do.
user access url A which results in the construction of page B
authoraization strategy kicks in when B is being constructed - and you throw
a RestartResponseAtInterceptPage(C) exception.
In fact, the current result is going to the admin page and trashing
the original URL while what I want was to save the original URL.
This way, after the login, I will be able to redirect to what the
user wanted first before the login.
I'm not sure if I am clear enough on what I want. The l
Hello Marc,
It is indeed very easy once you know where to look :)
Once the user is authenticated in the Login page you do something like this:
if (!continueToOriginalDestination()) {
setResponsePage(Application.get().getHomePage());
}
This will set the response page only when you got here dir
Hello group, it is again me for another question! :)
I'm trying to build an Authorization strategy around
AbstractPageAuthorizationStrategy.
For now, the authorization strategy is really simple as you will see in this
copy-paste of code :
protected boolean isPageAuthorized(Class pageClass)