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

ASF subversion and git services commented on WICKET-6503:
---------------------------------------------------------

Commit 16453f4a2e553e9bf9b2997d8615437fcc01392e in wicket's branch 
refs/heads/WICKET-6503_ajax_feedback_prepare from [~svenmeier]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=16453f4 ]

WICKET-6503 small optimization for ajax update


> Ajax refresh and feedback panel
> -------------------------------
>
>                 Key: WICKET-6503
>                 URL: https://issues.apache.org/jira/browse/WICKET-6503
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.28.0, 7.9.0, 8.0.0-M8
>            Reporter: Martin Makundi
>            Assignee: Sven Meier
>              Labels: ajax
>         Attachments: AjaxRequestTarget.diff.txt, 
> WICTKET-6503-feedbacks-prepare-last.zip, Wicket8_Quickstart-IListener.zip, 
> Wicket8_Quickstart-nested.zip, Wicket8_Quickstart.zip
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> For normal rendering we have:
> {{{{  /**
>        * We need to postpone calling beforeRender() on components that 
> implement {@link IFeedback}, to
>        * be sure that all other component's beforeRender() has been already 
> called, so that IFeedbacks
>        * can collect all feedback messages. This is the key under list of 
> postponed {@link IFeedback}
>        * is stored to request cycle metadata. The List is then iterated over 
> in
>        * {@link #prepareForRender()} after calling {@link #beforeRender()}, 
> to initialize postponed
>        * components.
>        */
>       private static final MetaDataKey<List<Component>> FEEDBACK_LIST = new 
> MetaDataKey<List<Component>>()
>       {
>               private static final long serialVersionUID = 1L;
>       };
> }}}}
> Should there be similar functionality built in for Ajax update? It seems to 
> be a typical problem that the feedback of an ajax update occurs too late.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to