[ 
https://issues.apache.org/jira/browse/WICKET-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199509#comment-13199509
 ] 

Daisuke Miyamoto commented on WICKET-1363:
------------------------------------------

Is this feature still supported in 1.5.x ?
                
> Support 
> RestartResponseAtInterceptPageException/continueToOriginalDestination() with 
> Ajax requests
> --------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-1363
>                 URL: https://issues.apache.org/jira/browse/WICKET-1363
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3.1
>            Reporter: Stefan Fussenegger
>            Assignee: Johan Compagner
>            Priority: Minor
>             Fix For: 1.3.2
>
>
> While RestartResponseAtInterceptPageException already works correctly with 
> Ajax requests (e.g. user is redirected to a login page), 
> continueToOriginalDestination() forwards the user to the Ajax request URL 
> (user will get a <ajax-respons>...</ajax-response> on his screen)
> Improvement: The user should rather be forwarded to a proper page. 
> Workaround: A custom PageMap implementation
> However, as the method setUpRedirect(RequestCycle) is private, deriving from 
> the default PageMap will require some ugly copy-paste in order to do so. This 
> could be avoided by a) making setUpRedirect(RequestCycle) protected and/or b) 
> introduce a protected method that constructs the interceptContinuationURL 
> inside setUpRedirect(RequestCycle).
> The custom behaviour could be: Redirect to the page the Ajax request belonged 
> to. Or even better: redirect to the Ajax call and render the complete page 
> (well, don't know how tricky that would be). 
> see also: 
> http://www.nabble.com/RestartResponseAtInterceptPageException-with-Ajax-td15607225.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to