Hi, Would you think that makes sense to remove the 'throws Exception' from a number of Camel API signatures as well as using unchecked exceptions instead?
While this may be a matter of opinion still debated, there are a couple resources that gives some guidelines on the topic and that may help answering that question: - "How to Design a Good API and Why it Matters" presentation and "Effective Java" from Joshua Bloch - https://docs.oracle.com/javase/tutorial/essential/exceptions/runtime.html I raise the question as I've encountered yet another case where checked exceptions fail to deliver on their promises, that is with functional interfaces (stream, lambda, ...) introduced in Java 8. There is a lot of resources out there describing the problem in details: - http://stackoverflow.com/questions/27644361/how-can-i-throw-checked-exceptions-from-inside-java-8-streams. - http://literatejava.com/exceptions/checked-exceptions-javas-biggest-mistake/ Hence the question. WDYT? Antonin
