Hi Christian, Thank you for your help, i am unable to upgrade the client so i had to make do with existing functionality. Unfortunately the very nice EIP you mentioned enrich does not exist in my version and the aggregator pattern doesnt quite do it either. I appreciate all these issues have been ironed out in future versions.
Just in case anyone is interested I manged to get around the problem in a couple of different ways. In one use case I was able to make use of the Multicast option where I did not care about the output of the JDBC component. In the second instance where I required the output of the JDBC component, well its header jdbc.updateCount output I used a custom producer template, exchange and message in order to fire of the message to the jdbc component, get back the header value and then fire off another message based on content to various other processors. Many thanks for all the help Graham -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JDBC-1-6-1-tp5716995p5717128.html Sent from the Camel - Users mailing list archive at Nabble.com.
