[ https://issues.apache.org/jira/browse/WICKET-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342450#comment-16342450 ]
ASF subversion and git services commented on WICKET-6503: --------------------------------------------------------- Commit d21bfe32525151a235afb3a6288ea11bcfa15329 in wicket's branch refs/heads/WICKET-6498_deferred_javascript_2 from [~svenmeier] [ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=d21bfe3 ] WICKET-6503 reintroduced markRendering - so rendered page or part checks hierarchy changes while rendering - stateless pages can be unmarked after beforeRender() in PageAndComponentProvider - prevent multiple onBeforeRender() calls for auto components that are already added > Ajax refresh and feedback panel > ------------------------------- > > Key: WICKET-6503 > URL: https://issues.apache.org/jira/browse/WICKET-6503 > Project: Wicket > Issue Type: Improvement > Components: wicket > Affects Versions: 6.28.0, 7.9.0, 8.0.0-M8 > Reporter: Martin Makundi > Assignee: Sven Meier > Priority: Major > Labels: ajax > Fix For: 8.0.0 > > 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: > {code:} > /** > * 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; > }; > {code} > 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 (v7.6.3#76005)