Hi Lance,
I did know about 'static structure, dynamic behaviour' but now understand it better in practice. :) It was indeed the parameters field null check - this really helped illuminate how things actually operate. Thanks for the help!! Much appreciated! Peter ----- Original Message ----- From: "Lance Java" <lance.j...@googlemail.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Thursday, 2 May, 2013 3:53:56 PM Subject: Re: [5.3] Mixin Base Class Affecting Initializer Parameters When In A Loop Do you realise that there is only 1 instance of the component and also 1 instance of the mixin? And that the same component/mixin is fired for all 5 iterations through the loop? It's part of tapestry's "static structure, dynamic behaviour". I think if you make sure to initialize all fields in setupRender() it should fix your issue. The null check in getParameters() might be the problem.
