The SwitchYard SQL binding offers a way to bind message variables to a SQL query specified in the binding: a List is passed, these are plugged into variables marked '#'.

SQL can also be specified on a property, "CamelSqlQuery". This allows us to over-ride the sql the reference binding would otherwise use, but does not offer the flexibility of binding objects from the message into the query.
ReferenceInvocation invocation = invoker.newInvocation("execute");
invocation.setProperty("CamelSqlQuery", "SELECT * FROM persons WHERE somecriteria .....");

Our customer finds this sub-optimal. This requires one binding per SQL operation, which leads to cluttered SY diagrams. It would be better if we could have a mechanism where SwitchYard provides both a query and a list of objects, having the infrastructure map the right values into the query. (Perhaps the query is provided via a message property, like case 2 above.)