Should we avoid issuing these?

We are implementing some checks that ask, for example, "Is the customer
allowed to do this?" And if the answer is no we're treating this as
irrecoverable.

Map this to irrecoverable according to Camel in Action Ch 5, Error
Handling. Yet this chapter barely touches irrecoverable errors, focusing
almost entirely on recoverable errors which are Throwables from the route.
The web site also seems to have the same focus.

Am I modelling this in my mind? When Camel thinks of irrecoverable, does it
consider this as a "stop the runtime" type of error or "stop the message"
type of error? And am I barking up the wrong tree entirely - should all
business logic checks that "fail" actually be considered recoverable
according to Camel?

N.B. I noticed Google has reference to a years-old discussion suggesting to
remove Fault, which has raised alarm bells in my thinking too.

Thanks,

James

Reply via email to