Github user svenmeier commented on the issue:
https://github.com/apache/wicket/pull/297
IMHO most people will want to show different contents depending on the
result of lazy loading - I doubt that anyone would want to give up polling but
keep the loading anymation - so they will need to transfer the result from
isContentReady() to getLazyLoadComponent() anyways. I don't like to use an enum
for that, as this will lead to even more enum values. It's just simpler to keep
this information as a member variable.
We could have joined isContentReady() and getLazyLoadComponent() into a
single method, but I tried to keep the API somewhat similar to 7.x.
Regarding the initial update interval: yes, I agree that this could be
improved. Note however that you are calling getUpdateInterval() too early in
bind() - at that moment not all AjaxLazyLoadPanel might exist yet.
Furthermore I made sure that at least one request is fired, to keep the
class backwards-compatible to 7.x with isContentReady() returning true by
default.
---
