GH-3765 Resolve Lookup ctor lazily via reflection #3781
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes spring-projects#3765 The `DefaultMethodInvokingMethodInterceptor` has several strategies for `default` method invocations in the messaging gateway. One of them is based on the `Lookup` constructor which causes a `WARNING: An illegal reflective access operation has occurred`. This can be done lazily when there is no `MethodHandles.privateLookupIn` in Java version used for the project. * Fix `OPEN` enum value for the `Constructor<Lookup>` to be resolved in a lazy manner via `Supplier` and `boolean` flag **Cherry-pick to `5.5.x`**
garyrussell
approved these changes
Apr 11, 2022
|
...and cherry-picked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3765
The
DefaultMethodInvokingMethodInterceptorhas several strategiesfor
defaultmethod invocations in the messaging gateway.One of them is based on the
Lookupconstructor which causesa
WARNING: An illegal reflective access operation has occurred.This can be done lazily when there is no
MethodHandles.privateLookupInin Java version used for the project.
OPENenum value for theConstructor<Lookup>to be resolved ina lazy manner via
SupplierandbooleanflagCherry-pick to
5.5.x