I've found it useful in the past to internally log the route definition / attributes in its hierarchical form (eg: endpoint uri, list of corresponding steps etc) to diagnose issues during route construction (eg: forgot missing .end() etc).
I've lost the source for being able to do this. Looking at the CamelContext I see the getRoutes() however it doesn't look like I can easily obtain the processors or steps beneath the route so I can log them. Specifically looking for step uri / component type (eg: to() / body() / process() / aggregate() etc and the definitions of each (eg: to(where), body(? what addtl parameters) etc). Note that a route.toString() is not ideal in this situation. -- ------------------------------------------- Craig Taylor ctalk...@ctalkobt.net
