So perhaps my CallableStatementCreator constructor should accept the values I wish to pass. Then I just create a new instance for each call.
The reason I am resorting to CallableStatementCreator is that I am trying to Spring-wrap a stored procedure call with a function call inside it. This morning I encountered the following SQL in JDBC code:
I'm trying to determine a systematic way to code Spring-wrappers for stored procedure calls that are more involved than simply "call myproc(x,y)".
call pkg_abc.p_get_contributions(?, ?, pkg_lookup.f_get_ctry(?), ?, ?)