Well, the vote is already started for the other RC. I think we *really* need a 1.3.0 of Camel asap and imho, non blocking bugs can be fixed in further bug fix release: I really suggest we release more frequently to avoid such problems. What about we do a bug fix release in a few weeks if needed ? Claus, wanna volunteer as the release manager for 1.3.1 ?
On Fri, Apr 4, 2008 at 9:49 AM, davsclaus <[EMAIL PROTECTED]> wrote: > > I am assuming we are building a new RC for the 1.3 release? > > In that respect we have a bug CAMEL-410 that I would like to get fixed and > included. I got the bug nailed down but want to polish and improve the > unit > tests before committing. I anticipate that I will be done at the end of > the > weekend at the latest. > > The bug is basically if you configure Camel to use 2 or more exception > handlers, then Camel could potentially pick the worst candidate for > handling > the thrown exception. By that I mean eg. a top level > .exception(Exception.class) instead of a user specific exception such as > .exception(MyBusinessException.class). > > I am introducing a strategy to resolve which is the best exception type to > handle the thrown exception in questions. The default strategy will be to > use the exception that is the closets match to the thrown exception. > > eg. java.net.ConnectionException will match java.io.IOException > eg. CamelExchangeException will match CamelException > eg. MyBusinessException will match MyBaseBusinessException > eg. NullPointerException will match Exception > > Well you might get the picture. > > A different strategy could be to use the ordering of how the exceptions > was > configured. Use the fist match that can handle it etc (top-down). > > /Claus > -- > View this message in context: > http://www.nabble.com/-VOTE--Release-Apache-Camel-1.3.0-%28RC4%29-tp16414633s22882p16487404.html > Sent from the Camel - Development mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
