Hi, after much of thought we decided it is best to not use such fields at all (Final or not). To prevent threading issues. We have many developers that code daily with T5 and we cannot babysit every decision devs make. Hence instructing to not use it at all guarantees better quality, although performance (might) suffer.
So, we moved to lazy initialization + service methods. - Ville -- View this message in context: http://tapestry.1045711.n5.nabble.com/As-the-type-Retain-is-deprecated-what-else-can-we-use-in-tapestry5-2-tp2643223p2643639.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
