[ https://issues.apache.org/jira/browse/WICKET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-399: -------------------------------------- Fix Version/s: (was: 1.3.0-rc3) 1.3.1 > Make RestartResponseAtInterceptPageException with a SignIn-type page work > correctly from AjaxFallbackLink > --------------------------------------------------------------------------------------------------------- > > Key: WICKET-399 > URL: https://issues.apache.org/jira/browse/WICKET-399 > Project: Wicket > Issue Type: Wish > Components: wicket > Affects Versions: 1.2.5 > Reporter: Nick Johnson > Assignee: Jean-Baptiste Quenot > Priority: Minor > Fix For: 1.3.1 > > Attachments: > 20070104-wicket-1.x-RestartResponseAtOriginalDestination, > 20070104-wicket-1.x-RestartResponseAtOriginalDestination.txt, > RestartResponseAtOriginalDestination.java > > > If you throw a new RestartResponseAtInterceptPageException from inside > onClick in an AjaxFallbackLink, Wicket does the right thing in redirecting > you to a SignIn page, but upon completing the sign-in, the > continueToOriginalDestination() call continues to the Ajax response (which > isn't particularly surprising). > It might be nice to have magic added to make this work seamlessly and restart > the onClick() somehow. It would be adequate to make the AjaxFallBackLink > behave as though fallback had happened in this situation. > A fairly simple workaround is to check in the Panel/Page to see if sign-in > has happened already and use a normal Link in the case that it hasn't. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.