i think the middle ground is to add RequestCycle#continueToOriginalDestination(). that way its your job to make sure you actually have a valid wicket scope before attempting to call that method.
-igor On Fri, Jun 28, 2013 at 11:49 AM, martin.dilger <martin.dil...@googlemail.com> wrote: > Hi Igor, > > We dont talk about different layers. > Even if my class would be named SignInAction, it belongs to the UI-Layer and > thats the only valid place, thats completely right. > Could be a Spring Bean for example, that throws some use case specific > authentication - exceptions (AuthenticationFailed, InvalidCredentials, > UsernameNotFound... ) that are handled at a central place - > RequestCycleListener for example. > > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/RestartResponseAtInterceptPageException-continueToOriginalDestination-tp4659907p4659915.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com.
