wicket-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Grigorov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (WICKET-6503) Ajax refresh and feedback panel
Date Sat, 02 Dec 2017 20:58:00 GMT

     [ https://issues.apache.org/jira/browse/WICKET-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Grigorov resolved WICKET-6503.
-------------------------------------
    Resolution: Not A Problem

Please use the mailing lists for asking questions!

> 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: 8.0.0-M8
>            Reporter: Martin Makundi
>              Labels: ajax
>   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)

Mime
View raw message