Hi Just to tell about the work I am currently doing https://issues.apache.org/jira/browse/CAMEL-6377
We have room to optimize the routing engine in Camel to make it more friendlier to end users in terms of - reduced stacktraces - faster and easier to debug the code if you single step through all the routing engine logic - potential optimization to skip over functionality that is turned off (eg such as tracer etc) - potential optimization to add new cross cutting functionality at runtime (though not currently the primary goal) - potential to skip using RedeliveryErrorHandler/DefaultErrorHandler if end user have not configured to use any kind of redelivery (the reason is that logic in this guy is excessive and is harder for people to debug) - reduce wrapping internal processors when not needed There is a sample route in the ticket where a stacktrace is forced being thrown. And the difference is 40 vs 28 lines in the stacktrace. And there is room for further optimization. The work is aimed at being non invasive on the current architecture and also backwards compatible. So far I have noticed a problem with the old behavior I have logged as: https://issues.apache.org/jira/browse/CAMEL-6378 -- Claus Ibsen ----------------- www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
