Hi Martin,
image the typical SignIn-Functionality.
You have a SignInPanel which only shows the necessary Form Components.
Then you have some sort of Bean like SignInActionXYZ, which has in its
perform method the typical flow:
if(signInSuccesful()){
//well, check if there was some interception
RestartResponseAtInterceptPageException.continueToOriginalDestination()
//no, ok, do some Other stuff
}
Of coure you are right, in many cases (but not all) it is valid and good to
work from Component.
BUT in some cases it is ok and good, to have this Possibility from other
Classes.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/RestartResponseAtInterceptPageException-continueToOriginalDestination-tp4659907p4659909.html
Sent from the Forum for Wicket Core developers mailing list archive at
Nabble.com.
