T5.3-rc-2 has the same behaviour.
Can someone tell me I'm not crazy and that I *should* see the
afterRender event firing? Or am I just missing something fundamental?
I know the Loop component uses afterRender to return true / false to
perform the loop, but I would still expect the Mixin render phase
event to fire... or is this not the case?
Steve.
On 2 November 2011 19:47, Steve Eynon <steve.ey...@alienfactory.co.uk> wrote:
> Hiya,
>
> I have this snippet of tml:
>
> <t:loop source="1..10" value="var:i" t:mixins="loopMixin">
> ${var:i}
> </t:loop>
>
> and this Mixin:
>
> public class LoopMixin {
> void beginRender() {
> System.err.println("LoopMixin: @beginRender");
> }
> void afterRender() {
> System.err.println("LoopMixin: @afterRender");
> }
> }
>
> I see the beginRender method called 10 times but the afterRender
> method is never called.
>
> Is this a bug or is it defined Mixin behaviour? I was under the
> impression Mixins should receive all component render phase events...?
>
> Steve.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
