On Mon, Oct 5, 2009 at 10:53 AM, Purcell, Chris (London) <[email protected]> wrote: > On Monday, 5 October, 2009 at 05:35, Claus Ibsen wrote: >> If you think that error handling is something that is easy >> then you cant be more wrong. Its hard. > > Sorry, wasn't intending to cause offense.
None taken. Error handling is just hard. > >> If you are using transacted routes then leave it to the >> underlying transaction manager to handle the error. > > So, as I understand it, that means if I get an error in a transacted > route, my only option is to rollback and take no other action? > That is the best option :) But you can do some mix and match but then be a bit more careful. The error handlers in Camel was designed to have this distinct separation from the start. The mix and match is just recently added in 2.0. >> If you mix and match with Camels onException and default >> error handlers etc. then you have to be much more careful. > > I'm happy to be more careful, I just can't find *any* way to mix and > match. > >> It would of course be much easier to somehow help you if you >> share your routes and more information what you want to >> archive and where you think there is a problem. > > As I said in my previous message, I've made a set of test routes > illustrating what I'm trying to achieve. I just don't know how you want > them provided. Should I email them to this group (unfriendly to those > with slow connections), or raise a bug report in JIRA so I can attach > them? > Yeah using the JIRA is very good. Then we wont forget. And you can attach files etc. > Chris > > ********************************************************************** > Please consider the environment before printing this email or its > attachments. > The contents of this email are for the named addressees only. It contains > information which may be confidential and privileged. If you are not the > intended recipient, please notify the sender immediately, destroy this email > and any attachments and do not otherwise disclose or use them. Email > transmission is not a secure method of communication and Man Investments > cannot accept responsibility for the completeness or accuracy of this email > or any attachments. Whilst Man Investments makes every effort to keep its > network free from viruses, it does not accept responsibility for any computer > virus which might be transferred by way of this email or any attachments. > This email does not constitute a request, offer, recommendation or > solicitation of any kind to buy, subscribe, sell or redeem any investment > instruments or to perform other such transactions of any kind. Man > Investments reserves the right to monitor, record and retain all electronic > communications through its network to ensure the integrity of its systems, > for record keeping and regulatory purposes. > Visit us at: www.maninvestments.com > TG0908 > ********************************************************************** > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
