I think really that *runtime* reflection is eliminated. I wonder if the bytecode generation is really faster than reflection. At any rate, to accomplish elimination of runtime reflection isn't the bytecode generation done at component creation time and the resulting bytecodes then pooled?
Bill On Wed, Aug 13, 2008 at 4:18 PM, Davor Hrg <[EMAIL PROTECTED]> wrote: > Javassist is used to generate > bytecode on the fly. > > prop: is a binding like any other, > look at the source of the > org.apache.tapestry5.internal.bindings.PropBindingFactory > > which in effect uses > PropertyConduitSourceImpl.create(targetClass, expression); > ehere expression is "foo" > > Davor Hrg > > > On Wed, Aug 13, 2008 at 11:04 PM, Alex Kotchnev <[EMAIL PROTECTED]> wrote: > >> The T5 main page (http://tapestry.apache.org/tapestry5/) indicates that >> reflection is virtually eliminated , which contributes to the improved >> performance of the framework. >> >> Can anybody point me to some resource (maybe source code, forum post) or >> give me a tip on how to see how this is done ? For example, if a component >> in a template specifies <t:textoutput value="prop:foo" /> or something >> similar, how is reflection avoided in resolving that the "getFoo" method >> needs to be called on the underlying component class ? >> >> Thanks, >> >> Alex Kotchnev >> > -- Bill @ PeoplePad --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
