Re: Camel 2.0 API - Discuss - Exchange.getException() change to Exception

2009/3/10 Claus Ibsen claus.ib...@gmail.com: Hi The Exchange.getException() method is based on Throwable. I think this is wrong and we should change it to Exception. We should let the java.lang.Error left alone to the JDK itself to handle it, so end users cannot try .. catch(Throwable) and

Re: Camel 2.0 API - Discuss - Exchange.getException() change to Exception

Hi, I just checked the servicemix-camel component , it will not be effect by this change. So I +1 for this change. Willem James Strachan wrote: 2009/3/10 Claus Ibsen claus.ib...@gmail.com: Hi The Exchange.getException() method is based on Throwable. I think this is wrong and we should

Re: Camel 2.0 API - Discuss - Exchange.getException() change to Exception

Committed revision 752465. On Wed, Mar 11, 2009 at 12:58 PM, James Strachan james.strac...@gmail.com wrote: 2009/3/11 Claus Ibsen claus.ib...@gmail.com: On Wed, Mar 11, 2009 at 12:20 PM, James Strachan james.strac...@gmail.com wrote: 2009/3/10 Claus Ibsen claus.ib...@gmail.com: Hi The

Camel 2.0 API - Discuss - Exchange.getException() change to Exception

Hi The Exchange.getException() method is based on Throwable. I think this is wrong and we should change it to Exception. We should let the java.lang.Error left alone to the JDK itself to handle it, so end users cannot try .. catch(Throwable) and thus hide java.lang.OutOfMemoryError etc. The