JBoss Reflect and javassist status
kabirkhan Apr 16, 2010 11:26 AMIn case the volcanic ashes clear and the planes work on Tuesday so I can go on holidays, here is the current status of the jboss-reflect on javassist implementation.
- <version.javassist>3.11.0.GA</version.javassist> + <version.javassist>3.12.0-SNAPSHOT</version.javassist> - <version.org.jboss.man>2.1.1.SP1</version.org.jboss.man> + <version.org.jboss.man>2.1.1.SP2</version.org.jboss.man> - <version.org.jboss.reflect>2.2.0.Alpha4</version.org.jboss.reflect> + <version.org.jboss.reflect>2.2.0-SNAPSHOT</version.org.jboss.reflect>
# Setup JBoss specific properties JAVA_OPTS="${JAVA_OPTS:+$JAVA_OPTS -Dprogram.name=$PROGNAME}" +JAVA_OPTS="${JAVA_OPTS:+$JAVA_OPTS -Dorg.jboss.reflect.spi.TypeInfoFactory=org.jboss.reflect.plugins.javassist.JavassistTypeInfoFactory}" JAVA_OPTS="${JAVA_OPTS:--Dprogram.name=$PROGNAME}"
$cd KABIR_JAVASSIST_REFLECT $~/svnmerge.py merge $svn commit -F svnmerge-commit-message.txt
The main thing I am looking at now is making the javassist implementation more performant. This is documented in JBoss Reflect Performance Javassist vs Introspection since using the javassist implementation is currently slower than using the introspection one. I'll let you know where I get in that thread before I leave.
It just occurred to me that another factor in currently making this slow _could_ be the classpools since we need to look CtClasses up there. I have not measured anything, but it is worth bearing in mind and investigating since it is an extra layer on top of the plain classloading which is used by the introspection implementation.
If I can think of anything else I will let you know on this thread before I go away.