Hi Koseki, On Mon, Mar 25, 2013 at 2:26 AM, koseki nonuyuki <koseki.nobuy...@gmail.com>wrote:
> 3)Print route information when error occured > Like printStackTrace() in Java, Camel can print routeTrace(), that make us > much easier to trace route when we encounter exception. > This would be a great improvement. Current stacktraces of Camel can be difficult to read as they're somewhat polluted with cross cutting concerns and "magic" interceptors and processors. A simple human-readable dump of a diagnostics context would help a lot. In the meantime, you can vaguely infer the place/context where the error could have occurred by checking these properties: * CamelFailureEndpoint => if the exception happend at an endpoint, it will contain that endpoint's URI * CamelToEndpoint => the last endpoint that Camel sent the Exchange to If the error occurred at a processor, we currently don't store which processor exactly, but it could make sense to create a new property CamelFailureProcessor to store the toString representation of the endpoint. Regards, *Raúl Kripalani* Enterprise Architect, Open Source Integration specialist, Program Manager | Apache Camel Committer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk
