Hi @msharpe ,
Glad to hear that work around is working for you. Did you verify that when you do that the exception doesn’t still make it to the binder’s error handler and published to the error queue (or requeued to the broker) anyway?
This obviously isn’t the cleanest solution so I’ll look into requesting an enhancement to the framework itself. I’m thinking it would be nice to specify an errorHandler on the input binding. Something that looks like this:
spring.cloud.stream.bindings.myFunction-in-0.errorHandler=handleError
And then handleError is just the name of a bean in the code that takes in an ErrorMessage . I believe this should allow the developer to also re-use that handleError bean across multiple input bindings as well.
What do you think? Would that satisfy your needs and be much cleaner? Can you think of any downsides?
Hope you have a great weekend.