The current implementation of JNI ids (jmethodID and jfieldID) is
* very inefficient - particularly in returning jmethodID from methodOop,
which involves multiple sequential searchs
* kludgy - separate implementations for methods, instance fields, and
static fields - none encapsulated
* does not support obsolete methods (methods which have been
non equivalently redefined with JVMTI RedefineClasses)
The first and last problem require this to be fixed in Tiger as part of the
JVMTI implementation.
The new implementation replaces an algorithm which is linear in the number
of methods and in the number of ids in the class with one that constant
time. It supports true obsolete methods and has a single encapsulated
implementation.
###@###.### 2003-04-25
* very inefficient - particularly in returning jmethodID from methodOop,
which involves multiple sequential searchs
* kludgy - separate implementations for methods, instance fields, and
static fields - none encapsulated
* does not support obsolete methods (methods which have been
non equivalently redefined with JVMTI RedefineClasses)
The first and last problem require this to be fixed in Tiger as part of the
JVMTI implementation.
The new implementation replaces an algorithm which is linear in the number
of methods and in the number of ids in the class with one that constant
time. It supports true obsolete methods and has a single encapsulated
implementation.
###@###.### 2003-04-25
- relates to
-
JDK-4763938 fieldacc003,fieldacc004: watchpoint on inherited field crashes VM
- Closed
-
JDK-4934202 JNIid need a proper support in SA code
- Closed
-
JDK-4639363 Java Platform Profiling Architecture (JSR-163)
- Resolved