[
https://issues.apache.org/jira/browse/WICKET-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-3010.
-----------------------------------
Assignee: Igor Vaynberg
Resolution: Won't Fix
this is a big time edge case, and i dont think we will support it.
an easy workaround is instead of calling setresponsepage append javascript to
the target that will redirect.
> RequestCycle.setResponsePage should defer switching to
> BookmarkableRequestTarget until finishing responding to currrent target
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-3010
> URL: https://issues.apache.org/jira/browse/WICKET-3010
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.10
> Reporter: Vladimir Kovalyuk
> Assignee: Igor Vaynberg
>
> Once setResponsePage is called the AjaxRequestTarget is pushed down in the
> list of request targets and AjaxRequestTarget won't be called anymore because
> AbstractRequestCycleProcessor.respond invokes the current request target only.
> My page has some ajax links that delegates handling to different module and
> link does not know whether redirect happens. The link still has to update
> some components. But in case of redirect all the updates aren't applied and
> backbuttoning shows old state (actually with ajax indicator covering all the
> page so any element is not clickable).
> I believe it makes sence to defer switching to different request target until
> finishing responding on ajax request.
> I found WebApplication.logResponseTarget(IRequestTarget target) as the place
> where I can actually apply deferred redirect. Please don't kill or make this
> method final.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
