-
Enhancement
-
Resolution: Unresolved
-
P4
-
23
-
None
-
In Review
Core reflection's generic signature parsing uses an ancient library with outdated visitor pattern on a tree model and contains unnecessary boilerplates. This is a duplication of ClassFile API's signature model. We should just move to ClassFile API, which is more throughoutly tested as well.
This migration will not affect the implementation classes of java.lang.reflect.Type, except the lazy expansion will happen from the CF tree objects instead of legacy tree objects. New regression tests will ensure backward-compatible behavior with malformed signatures and missing classes or interfaces in signatures.
This migration will not affect the implementation classes of java.lang.reflect.Type, except the lazy expansion will happen from the CF tree objects instead of legacy tree objects. New regression tests will ensure backward-compatible behavior with malformed signatures and missing classes or interfaces in signatures.
- is blocked by
-
JDK-8350704 Create tests to ensure the failure behavior of core reflection APIs
-
- In Progress
-
- relates to
-
JDK-8351103 JVMS class signature specification disagrees with implementation
-
- Open
-
- links to
-
Review(master) openjdk/jdk/19281