Done: https://issues.apache.org/jira/browse/WICKET-5460
On Fri, Jan 3, 2014 at 10:16 PM, Sven Meier s...@meiers.net wrote:
This could be a bug. Could you create a quickstart please and attach it to a
JIRA issue?
Many thanks
Sven
On 01/01/2014 07:38 PM, Martin Geisse wrote:
Hi,
thanks
This could be a bug. Could you create a quickstart please and attach it
to a JIRA issue?
Many thanks
Sven
On 01/01/2014 07:38 PM, Martin Geisse wrote:
Hi,
thanks for the quick response. Just to be sure, I added code to detach
the model after changing it, but nothing changed in behavior. In
Hi,
any news on this? Is this a bug? If so, I'd open a ticket on Jira.
Unfortunately, I don't know of a simple solution yet.
Greetings,
Martin
On Wed, Jan 1, 2014 at 7:38 PM, Martin Geisse
martingei...@googlemail.com wrote:
Hi,
thanks for the quick response. Just to be sure, I added code to
Hi,
I'm having a problem with a ListView that displays an outdated list. In my
test, the ListView uses a LoadableDetachableModel that loads from a
static variable just to make sure the model is independent from any page
instance. As far as I can tell, this problem has nothing to do with the
Hi,
first of all, sorry for double-posting. It seems like I triggered some
strange keyboard shortcut in Gmail before I was finished writing that
mail... :(
I'm having a problem with a ListView that displays an outdated list.
In my test, the ListView uses a LoadableDetachableModel that loads
from
Hi,
if I read its javadoc correctly, #internalPrepareForRender(false) should
not mark the page as rendered (thus the false parameter).
If your link modifies the ListView's model, it should call #detach() on
it. Otherwise it will show stale data on next rendering. This doesn't
have anything
Hi,
thanks for the quick response. Just to be sure, I added code to detach
the model after changing it, but nothing changed in behavior. In this
case, LoadableDetachableModel only caches a *reference* to the
underlying java.util.List, which is shared by all instances of the
model class (it comes
