How to implement a functional-programming style of exception-processing with Spring-Integration ? i.e. instead of letting the exception bubble up to the caller or to s
