You're right, this is already too complex for a tutorial and getting side tracked over those kinds of details in meaningless. Just saying "lightning fast and type-safe" is good enough.
I'm itchy about this subject because I did work with a client who was evaluating Tapestry and they had an enterprise-wide restriction on no runtime reflection ... i.e., they would not use T4 because of OGNL. I believe even they would be ok with the kind of reflection that T5 does (for analysis purposes) given that the end result is true bytecode, ready to be optimized by Hotspot. On Thu, Nov 18, 2010 at 5:23 PM, Josh Canfield <[email protected]>wrote: > I'm pretty sure that the footnote "Tapestry does _not_ use reflection to > implement property expressions." is incorrect. > > As I understand it, property expressions are built using the > PropertyConduitSource which uses reflection to determine the type and > available properties for each step in the expression. Right or wrong, I'm > not sure why the distinction is made here anyway... > > Josh > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
