9d8393eb3e
* Miscellaneous improvement for end-user experience Related to https://stackoverflow.com/questions/66428239/ineligiblemethodexception-found-more-than-one-parameter-type-candidate-spring Related to https://stackoverflow.com/questions/66397350/spring-integration-how-do-i-call-the-spring-integration-from-spring-controller The exception thrown from gateway method call for `null` arg is not clear that it cannot be `null` * Improve `GatewayMethodInboundMessageMapper.mapArgumentsToMessage()` exception message to show args and explain that it cannot be resolved to `null` When more than one params are candidates for method invocation, the `MessagingMethodInvokerHelper` throws an `IneligibleMethodException` which outcome is not clear what to do * Add `@Payload` annotation recommendation into an exception message to make the reason more cleaner * Some other code style clean up in the `MessagingMethodInvokerHelper` * * Fix `PseudoTransactionalMessageSourceTests.testCommit()` for better coverage * Apply suggestions from code review Co-authored-by: Gary Russell <grussell@vmware.com> Co-authored-by: Gary Russell <grussell@vmware.com>