KameletBinding - Make error handler more simpler

[davsclaus]

A binding is intended to be high level and fairly simple.
https://camel.apache.org/camel-k/1.7.x/kamelets/kameletbindings-error-handler.html

I wonder if we have not made the error handler a bit too complex with the bean and ref. What is the purpose of those. As they require the user to implement a custom error handler builder (which nobody really does in core camel).

I wonder if we can deprecate and remove those, or did you find a use-case for them somehow in camel-k?

[davsclaus]

@squakez any thoughts?

[squakez]

Yeah, I think the direct usage of them can be hidden to the final user, but cannot be removed (at least ref) as it's the foundation of the feature itself (see

camel-k/pkg/trait/error_handler.go

Line 97 in 2ef7836

"ref": t.ErrorHandlerRef,

). When I developed originally the feature, I exposed all the low level implementations to collect feedback on possible advanced use case. I don't see any added value to the user, so, I agree we can remove the option. Also @lburgazzoli was involved on the design, maybe he had in mind some other use case I ignore.