Best way to start is by spending 25$ and get this book http://www.indiegogo.com/tapestry5book
It explains everything you want to know. Tapestry Pages are Singleton. One Instance of Page is used between multiple threads. Page can either save data in application session OR page session. Application session is not recommended unless it is absolutely necessary to do so because your application might be running in cluster environment. When one node of cluster goes down, all sessions are replicated to other server. Page session is probably implemented by help of ThreadLocal. Each Thread has it's own share of memory. If you declare any variable with final of static in your page, those variable will be visible to all threads. You can also choose to declare variable such that they are discarded immediately after thread is served. I would recommend you to start reading book and subscribe on this mailing list. Also go back and look at historical threads. There is lot to learn. Tapestry is using black magic ( :D ) inside it's guts called as Plastic. You should visit Howard's video session talking about Plastic which is very important piece to know. You also want to understand how spring bean injection work. It will give you some basic idea why tapestry came up with IOC ( similar like tapestry, goose, other frameworks which injects beans... IOC solves some of the problem those other framework couldn't solve. ). Hopefully this leads you in right direction. Best of luck. -- View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-by-JEE-standard-tp5715543p5715545.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
