Hi Howard, Thanks for you soon reply. I have a doubt with repesct to you reply. If in tapestry 5.2 it works with only one instance (like in a servlet) then it is imposible to make the maching in a POJO/tml because this elements always is going to be a mutable objects (in the same way that a servlet with global variables).
Then for this example (in tapestry 5.2) how do you make the machting the tml fields with java class without all users see the data bleed. Would you mind to provide an exanple for the correct use? Thanks in advance Kind Regards -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-Request-data-shared-in-different-client-browser-tp3405994p3406223.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
