How about creating a processor that calls upon the filter and captures the resultant exchange? Then if that goes well use a producer template to send out both the resultant exchange and the original exchange concurrently.
No transaction required and you'll achieve higher throughput. -- View this message in context: http://www.nabble.com/Newbie-Question--2%3A-Transactional-Client-tp22122816p22179744.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
