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
Now that class proxies can be generated at build-time and reused consistently (see #28115), we need to integrate that in our AOT processing. As part of this, the proper hint should be inferred so that the class can be discovered at runtime.
The text was updated successfully, but these errors were encountered:
This commit expands GeneratedClassHandler to allow invocation of
declared fields and methods. Generated proxies have a number of
internal fields and methods that are invoked via reflection.
See gh-28954
This isn't complete without method invocation hints on the target class, as stated by @jhoeller:
I'm afraid that's the case since all the interceptor callbacks behind the proxy are Method-based, just like behind a JDK proxy. The naming arrangement is stable and in our control, so taking everything before the first $$ (for a class name to provide reflection for) should be a reliable way to handle it.
This commit updates the hints of a Cglib proxy's target type so that
methods can be invoked and constructors can be introspected. The former
is needed as a cglib proxy invokes the target type via reflection. As
for that latter, this is required at least by
Enhancer#filterConstructors.
See gh-28954
Now that class proxies can be generated at build-time and reused consistently (see #28115), we need to integrate that in our AOT processing. As part of this, the proper hint should be inferred so that the class can be discovered at runtime.
The text was updated successfully, but these errors were encountered: