[
https://issues.apache.org/jira/browse/WICKET-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov updated WICKET-4675:
------------------------------------
Summary: Process Ajax responses in one go (was: Allow the server to
control which Ajax channel is used to process ajax responses on a per component
basis)
> Process Ajax responses in one go
> --------------------------------
>
> Key: WICKET-4675
> URL: https://issues.apache.org/jira/browse/WICKET-4675
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.0.0-beta3
> Reporter: Christian Oldiges
> Assignee: Martin Grigorov
>
> situation:
> - one component is replaced via several ajax channels.
> - the processing of the reponse steps of those channels may be interleaved.
> - the ajax response may contain DOM replacements (including modified IDs and
> component paths) and event handler assignments
> The correct order for two concurrent ajax requests executed over 2 seperate
> channels would be:
> DOM replacement
> event assigment
> DOM replacement
> event assignment
> Currently something like this may happen:
> DOM replacement
> DOM replacement
> event assignment
> event assignment
> The event assignment fails when the component ids change during the DOM
> replacement.
> Also it is required that the second batch of event assigments is executed
> after the first batch
> Possible solution - Add a new method to assign an Ajax Channel per component
> for the ajax response:
> target.add(component, channel);
> This would allow to schedule the response processing to the ajax channel on a
> per-component basis instead of a per-request/response basis.
--
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
