Rickard, You mention before that we could optimize a lot if we could get hold of the Method index, and stick it into an array for quick lookup instead of the hashmap now in place. You wanted to use some other bytecode manipulator for it.
Perhaps the "slot" field in the java.lang.reflect.Method class could help. It holds the index of the method in the declared class. Not sure if still problematic, as I suspect it could become a question of "which interface" instead, but I thought I mention it just in case anyway. Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
