Guten Tag Sven Meier,
am Mittwoch, 18. März 2020 um 10:04 schrieben Sie:

> what IItemReuseStrategy are you using?

> DefaultItemReuseStrategy creates new items on each render, which leads
> to new ids.

I didn't care yet and can't find anything regarding that strategy, so
I guess it's the default one. While I indeed render the same page
multiple times within the same test, things look like the following:

> try (VwrCtxThreadScoped scopedCtx = new VwrCtxThreadScoped(ctx0))
> {
>       VwrHtmlApp      app     = new VwrHtmlApp();
>       WicketTester    tester  = new WicketTester(app);
>       VwrHtmlPage     page    = new VwrPgMcsmSummary();
>       tester.startPage(page);
>       this.wicketAssertBase(tester, page);
> tester.assertVisible("html:body:meterCnt.someMonth.pnMcsmSummary:resultsContainer:noResults");
>       tester.destroy();
> }

So each invocation works with new instances of everything in theory.
Even the results to render themself change, as those are contained in
"ctx0", "ctx1" and "ctx3". 

So, shouldn't each of those blocks start freshly in theory?

Mit freundlichen Grüßen,

Thorsten Schöning

Thorsten Schöning       E-Mail:
AM-SoFT IT-Systeme

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to