Well, I thought I would post a note about what I did to actually get this to
work. I think that this still seems like a work around and that tapestry
should make the dealings of its generated internal ids more transparent.
Also, I didn't come up with this on my own, so thank Fanf for pointing m
I have been thinking about this problem a little further and I don't think
that adding a static id on the zone is going to work. The problem that I
have is that this Zone lives inside a component. This component could be
used multiple times and that would break the uniqueness of the id of the
zon
actually it seems to be a more general problem. if we take two zones, outer
and inner one, everything linked to the inner zone (via t:zone="blahblah")
stops updating if zone had been updated previously. simply, T5 updating
inner zone immediately changes its zone ID.
ok, i know. it's a namespaci
