Just a side note, this has caught a few users over time (since t5.1).
Boris' expected behaviour does not seem to me to be too unrealistic an expectation! Depending on your personality type ;) you may even consider this a bug.
Maybe the zone re-rendering process should handle this client id changeover gracefully?
p. On 22/01/2012 8:38 AM, bhorvat wrote:
Hm... Yea this worked perfectly. I know that the new id is generated but I was under the impression that tapestry eventlink will adapt to that since I did set which zone to target I thought that once everything is refresh that will also refresh... Thank you both for assistance :) -- View this message in context: http://tapestry.1045711.n5.nabble.com/Zone-and-Eventlink-refresh-problem-tp5161722p5163366.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
