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
While working on #30692, I noticed that we currently do not invoke shadowed package-private init/destroy methods declared in a different package.
Instead, we only invoke the last such init/destroy method found in the type hierarchy.
We should therefore track "non-visible" package-private init/destroy methods by their fully-qualified method name, analogous to how we track private init/destroy methods.
Prior to this commit, if an init/destroy method was package-private and
declared in a superclass in a package different from the package in
which the registered bean resided, a local init/destroy method with the
same name would effectively "shadow" the method from the different
package, resulting in only the local init/destroy method being invoked.
This commit addresses this issue by tracking package-private init
methods from different packages using their fully-qualified method
names, analogous to the existing support for private init/destroy
methods.
Closesspring-projectsgh-30718
Overview
While working on #30692, I noticed that we currently do not invoke shadowed package-private init/destroy methods declared in a different package.
Instead, we only invoke the last such init/destroy method found in the type hierarchy.
We should therefore track "non-visible" package-private init/destroy methods by their fully-qualified method name, analogous to how we track
private
init/destroy methods.Related Issues
private
init/destroy methods are not supported in AOT mode #30692The text was updated successfully, but these errors were encountered: