Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Unknown
Description
We would like to be able to categorize an error (exception thrown) by Camel routing engine whether that error happend in the consumer/source, during processing (routing) or in the producer/sink (sending to external system).
This can better assist where a problem lies, i.e. source and sink are related to external systems, processing is related to Camel or custom end user integration/business logic.
We can also have some kind of SPI to introspect the thrown exception and error message, to enrich error details.