2012/3/9 Łukasz Dywicki <[email protected]>: > I think that support for named parameters is something we could provide. > Another thing is to let users provide own implementation of > PreparedStatementCallback to map more complex parameters. I use camel-sql and > as you, have same problem with conversion to list.. >
Good ideas. Feel free to create a JIRA. And as always we love contributions. > Best regards, > Lukasz > > Wiadomość napisana przez dunnlow w dniu 5 mar 2012, o godz. 18:15: > >> I wanted to add, I'm using Spring DSL routes. >> >> Also after some more thought, I'm thinking of two things to try: >> >> 1) come up with a way to create the SQL component parameter definition list >> on the fly based upon the order of the headers. >> >> 2) Create a converter for my POJO bean from Bean to List and put that pojo >> in the message body; hoping that Camel will use that converter to create the >> list. The converter will be responsible for doing a DESCRIBE on the >> database and then creating the resulting List using the correct order. >> >> Any thoughts? >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/SQL-Component-parameter-order-tp5538064p5538182.html >> Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
