ghillert/spring-integration — comment on commit 9761c030fa12e756c1a9510525362ef2c069b0dc
File: spring-integration-jdbc/src/main/java/org/springframework/integration/jdbc/StoredProcExecutor.java line 158
By ghillert:

You can provide one or the other (sqlParameterSourceFactory).

I don't see a real use-case where both need to be set at the same time. If you don't use explicit stored-procedure-parameters you can supply any type of sqlParameterSourceFactory but if you use stored procedure parameters, you must supply an instance of ExpressionEvaluatingSqlParameterSourceFactory. This is probably a rather unlikely usage-scenario as is.

In a very theoretical scenario you could argue for a mix and match - you provide explicit parameters but some other parameter are derived implicitly from the payload. Is that what you elude to? So in that sense you could argue for having more than one sqlParameterSourceFactory. But do we really want to? Would that be too esoteric?