• b25

        In order to reduce the size overhead of Type Annotations on reflective objects, and in order to provide the desired semantics with respect to redefine classes for type annotation, the core reflection code needs a way to query the VM for the current type annotation bytes for a given Method or Field.

        This was done for regular annotations in issue JDK-6422541 where the following was added:

        Constructor - needs JVM_GetMethodAnnotations() and
                      JVM_GetMethodParameterAnnotations();
                      does not need JVM_GetMethodDefaultAnnotations()
        Field - needs JVM_GetFieldAnnotations()
        Method - needs JVM_GetMethodAnnotations(),
                      JVM_GetMethodDefaultAnnotations, and
                      JVM_GetMethodParameterAnnotations()

        For type annotations only

        JVM_GetMethodTypeAnnotations() and
        JVM_GetFieldTypeAnnotations()

        are needed due to Constructor being a method from the VM's point of view. Also default values are handled by the previous jvm.h interface.

              jfranck Joel Borggrén-Franck (Inactive)
              jfranck Joel Borggrén-Franck (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: