Hi, I just noticed that some creative soul has created static object populator method in a project that I work in. This method is very handy, and is used through out the system now :)
It uses T5 PropertyAccess service, but the static method doesn't receive it as parameter - it is instantiated inside the method using new PropertyAccessImpl();. The implementation has caches and I tried to move propertyAccess to be private static final in the populator class. This resulted really substantial performance improvment. (Nearly twice as fast populations.) Now the only question is: is the PropertyAccess service thread safe to use? What about the ClassPropertyAdapter.set(object, string, object) and ClassPropertyAdapter.get(object, string)? - Ville -- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-PropertyAccess-and-thread-safety-tp2841770p2841770.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
