fix: Preserve NULL Parameters in case of AOP Proxy #35014
+97
−21
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.
I have seen a case where NULL argument is passed explicitly in the function call but it is taking default value instead. Below are the function signatures.
This is specific to suspending functions and optional parameters only. Upon checking the code, I have below findings.
Below is the change introduced in spring-aop from version 6.0.21 to 6.1.1, Earlier we are directly invoking the method via reflection but now
CoroutinesUtils.invokeSuspendingFunction
is getting invoked which is filtering the NULL values.spring-aop change:

As a part of this PR, I have introduced one more method in
CoroutinesUtils
which preserves the NULL values passed in arguments. This is being invoked via AOP Only and keeping the other flow remains as it is.Let me know if you need any reproduction steps or additional feedback related to the code changes. I'm happy to contribute wherever I can.