You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it is impossible to reflectively access elements of lambdas and Proxy classes in Native Image. The reason is that the format of reflect-config.json can not refer to lambda and proxy types. The current JSON element name can't be used as lambdas and proxies don't have a stable class name to refer to.
This proposal would allow reflective access to proxy classes and lambda classes in Native Image by supporting proxies and lambdas in reachability metadata.
Goals
This proposal should add two new types of elements to reflect-config.json and jni-config.json:
For proxies we propose referring to them via the list of interfaces in the following way:
TL;DR
Currently, it is impossible to reflectively access elements of lambdas and Proxy classes in Native Image. The reason is that the format of
reflect-config.json
can not refer to lambda and proxy types. The current JSON elementname
can't be used as lambdas and proxies don't have a stable class name to refer to.This proposal would allow reflective access to proxy classes and lambda classes in Native Image by supporting proxies and lambdas in reachability metadata.
Goals
This proposal should add two new types of elements to
reflect-config.json
andjni-config.json
:These elements would then be accessible via reflection at runtime.
Non-Goals
Support the predefinition of lambdas or proxies.
Make
proxy-config.json
unnecessary, although this could be considered.The text was updated successfully, but these errors were encountered: