Check Wicket's Ajax console for any output - is the request triggered to
load the lazy load component?
Sven
On 12/17/2013 09:42 PM, Entropy wrote:
Hi, it's me again, and I am still converting from 1.4.7 to 6.12. I think I
am starting to get down to the last few errors.
I have an AjaxLazyLoadPanel that loads a grid of data that takes a little
time to load. It worked fine in the 1.4.7 version of the app, though there
are code changes from the conversion, they seem to have been driven by the
compile differences.
Anyway, here's what it looks like:
add (new AjaxLazyLoadPanel("assetInfos"){
@Override
public Component getLazyLoadComponent(String id);
EQShareInfoPanel myPanel = new EQShareInfoPanel(id,
getSharingInfos(searchBean), false);
myPanel.setOutputMarkupId(true);
return myPanel;
}
});
<div id="contentmain">
<div wicket:id="assetInfos" class="tablepanel"></div>
</div>
I put a breakpoint in the getLazyLoadComponent methods above and the
breakpoint is never reached. I already removed the jQuery-min reference
from this page as that had blocked the other ajax control on this page (as
might be remembered from my thread yesterday). So the code inside that
method isn't the problem.
Any ideas where to start looking?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/AjaxLazyLoadPanel-in-wicket-6-tp4663083.html
Sent from the Users forum 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
