-
Notifications
You must be signed in to change notification settings - Fork 1.1k
MessagingMethodInvokerHelper should disregard synthetic methods #3912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Interesting...
|
Any chances to see such a service in Groovy, which, as you said, comes with synthetic methods? Thanks |
Could you clarify? Are you asking for a code sample that produces the problem? I'm not at the office, but this should reproduce the error:
|
I have just confirmed that proposed Thank you! |
Fixes spring-projects#3912 **Cherry-pick to `5.5.x`**
Fixes #3912 **Cherry-pick to `5.5.x`**
Fixes #3912 **Cherry-pick to `5.5.x`**
In what version(s) of Spring Integration are you seeing this issue?
5.5.14
Describe the bug
I have a service object written in Groovy that I'm providing to the
handle
instruction on a DSL integration flow. This service method has a single public method plus some private fields and closures; the presence of the closures causes the generation of some synthetic methods to access the private fields in the top-level class. TheMessagingMethodInvokerHelper
throws an exception claiming ambiguous methods because it's processing the synthetics as fallbacks.To Reproduce
Pass a class that carries synthetic methods to
handle
.Expected behavior
I expect synthetic methods to be excluded. Specifically, at
MessagingMethodInvokerHelper:776
, the existing conditionshould be logically equivalent to
The text was updated successfully, but these errors were encountered: