jsinai wrote:
>
> I have the same problem with refreshing fragments via ajax. The problem
> does not exist in 1.4.0 and earlier. It started in 1.4.1+, I believe.
>
I have downloaded the source for 1.4.9 and made the change below in
AjaxRequestTarget.java, which fixed the problem for me. The change is
commenting out the check "if (!containsAncestorFor(component))".
I verified that this change was made between 1.4.0 and 1.4.1, although the
release notes make no mention of it. We make heavy use of fragments, so this
is a big problem for us.
private void respondComponents(WebResponse response)
{
// TODO: We might need to call prepareRender on all components
upfront
// process component markup
Iterator<Map.Entry<String, Component>> it =
markupIdToComponent.entrySet().iterator();
while (it.hasNext())
{
final Map.Entry<String, Component> entry = it.next();
final Component component = entry.getValue();
final String markupId = entry.getKey();
// if (!containsAncestorFor(component))
// {
respondComponent(response, markupId, component);
// }
}
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/refreshing-fragment-tp2286189p2315451.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
