the camel page on transactions shows you how to do an XA transaction manager. :)
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Hardcore Java (2003) and Maintainable Java (2012)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 <http://www.linkedin.com/pub/robert-simmons/40/852/a39>* On Sat, Jan 4, 2014 at 5:10 PM, Krzysztof Sobkowiak < [email protected]> wrote: > Hi > > Are there any samples how to develop such requirement with camel? > > Krzysztof > > > On 04.01.2014 22:04, Pontus Ullgren wrote: > >> It all depends on your requirements and how your database and the >> system consuming from the second queue is designed. >> >> If the write operation to the database and the system consuming from >> the second queue is idempotent, ie they can both gracefully handle >> that the same message is processed twice. Then you can think about >> skipping XA. >> >> If this is NOT the case, or if you are unsure what would happen if the >> same message is consumed twice, then you will need XA. >> >> In the scenario you describe I would defiantly consider using XA just >> to be safe. >> >> Pontus >> >> On Fri, Jan 3, 2014 at 11:48 PM, Larry Meadors <[email protected]> >> wrote: >> >>> Just to be clear here...if you're doing this: >>> - get a message from JMS broker A >>> - write to database >>> - put a messages in a queue on JMS broker A >>> >>> Should you or should you not need XA? >>> Larry >>> >> > > -- > Krzysztof Sobkowiak > > JEE & OSS Architect | Technical Architect @ Capgemini > e-mail: [email protected] <mailto:[email protected]> | > Twitter: @KSobkowiak >
