Wait, Javassist has documentation now ? :-) The bytecode stuff has a number of advantages over reflection. It's 2x to 5x faster (that number shifts with every JDK release). It can be inlined and optimized by Hotspot. We don't waste time creating Object[] arrays for parameters and boxing and unboxing primitives.
My attitude is that, for any particular method invocation, the difference is minuscule; virtually undetectable. However, multiplied by the thousands of method invocations per request it might start to be measurable. Meanwhile, I'm looking, for 5.1, at ways to improve performance, especially on IoC service proxies. On Thu, Aug 14, 2008 at 9:14 AM, Thiago H. de Paula Figueiredo <[EMAIL PROTECTED]> wrote: > Em Wed, 13 Aug 2008 18:50:41 -0300, Bill Holloway <[EMAIL PROTECTED]> > escreveu: > >> 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? > > The bytecode generation is made once and used many times. It is only > generated again if you change your page or component or mixin. > > By the way, the Javassist documentation is a nice reading. :) > > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
