On Mon, Nov 22, 2010 at 4:32 PM, Olivier.Roger <[email protected]> wrote: > > I am sorry, I am not sure to understand how transacted works on the > aggregator component. > > Does adding .transacted() to the aggregator include the repository > operations inside transactions? > Then, is this necessary when the aggregator already is in a transacted route > ? Or does it has to be specified so that the operation could join the > current transaction ? >
Nah you may be right that it should be more tightly integrated into your custom repository. But there should be code we can reuse / stand on top of from the code in Camel already. So its maybe a matter of depending on camel-spring, and then have the TM injected into the repo. And then take a look at how we do in camel-spring in the TransactedErrorHandler where we can kinda do the logic in a spring method. Kinda like what we do for hawtdb as well. Anyway if you manage to have the code shared / donate to Apache we can work on getting those final pieces into places so we can have it working with transactions. Would be cool if you could prepare unit tests which can run using an embedded database such as HSQLDB or something similar. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Aggregator-Persistence-tp2800301p3275510.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
