Re: Unexpected component-ID "2" for 1 child of repeating view.

Hi, that looks fine. I was thinking of longer tests: - start page - click link* - click button* - ... - check table contents (* initiating a page render) You could put a breakpoint in RepeatingView#newChildId() and check who's creating new items. Have fun Sven On 18.03.20 12:38, Thorsten

Re: Unexpected component-ID "2" for 1 child of repeating view.

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

Re: Unexpected component-ID "2" for 1 child of repeating view.

Hi Thorsten, what IItemReuseStrategy are you using? DefaultItemReuseStrategy creates new items on each render, which leads to new ids. Maybe testing your additional panels initiates additional pages renderings? Have fun Sven On 18.03.20 09:29, Thorsten Schöning wrote: Hi all, I have some

Unexpected component-ID "2" for 1 child of repeating view.

Hi all, I have some test in Wicket which renders a HTML-table using some "DataView" and in that test I'm distinguishing the cases 0, 1 and 3 result rows. The following is an example for 1 and 3 rows: > assertNotNull(tester.getComponentFromLastRenderedPage("html:body:meterCnt.someMonth.pnMcsmSumma