If I understood you correctly, you want to know from where this Exchange
which holds the exception, have you tried something like
`exchange.getFromEndpoint` or `exchange.getFromRouteId`? Which as I
understood should gives from which endpoint this exchange has been
originated from. However, I think
The Camel community announces the immediate availability of the
release Camel K Runtime 1.0.1. This release contains all the runtime bits
used by Camel-K,
fixes and improvements.
The artifacts are published and ready for you to download either
from the Apache mirrors or from the Central Maven
