Maybe use a groupedExchange, see: http://camel.apache.org/aggregator2.html ?
2012/8/7 Thomas Johansen <thxm...@gmail.com>: > I'm not sure what this implies, Scott. > > My use case is to have a transaction started on a first exchange, and then > have X exhanges on the same transaction. It should first be committed when > some external event happens, like a control message is seen (possibly from a > separate control queue), after X number of messages or something. I'm sure > Camel provides some options for mechanisms to use here? In my case I need to > aggregate X records into a single file. > > Thomas > > > Den 7. aug. 2012 kl. 14:50 skrev Scott England-Sullivan <sully6...@gmail.com>: > >> I will take a look at it tonight. Plan is to add batch support by having >> the Producer and Consumer endpoints support a List of Messages. Once in >> place TX would be automatically supported as it is called as a >> Synchronization upon completion of the Exchange. >> >> Thoughts? >> >> On Tue, Aug 7, 2012 at 6:21 AM, Christian Müller < >> christian.muel...@gmail.com> wrote: >> >>> +1 >>> Would like to see this feature too... >>> >>> Sent from a mobile device >>> Am 07.08.2012 10:49 schrieb "Thomas Johansen" <thxm...@gmail.com>: >>> >>>> Hi, >>>> >>>> As I understand the JMSComponent/ActiveMQComponent cannot support batched >>>> transactions due to the use of Spring's DMLC. With this new SJMSComponent >>>> there should be possibilities to implement this, I guess? >>>> >>>> BR, >>>> Thomas >>>> >>> >> >> >> >> -- >> -- >> Scott England-Sullivan >> ---------------------------------- >> FuseSource >> Web: http://www.fusesource.com >> Blog: http://sully6768.blogspot.com >> Twitter: sully6768 -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
