Thanks a million for the response Hadrian. That was what I kinda suspected (i.e. legacy reasons). Your response makes me very confident now that wrapping the offending methods is the correct action for me right now (it's pretty trivial for me to do anyway). That way I get rid of the nasty (i.e. 'noisy') Checked Exceptions in my code, and I may also be isolated from at least some of the breaking changes that may come in Camel 3.0 (but of course you're right, backward compatibility will indeed be a huge issue right across the Camel codebase, if it ever actually happens...!).
-- View this message in context: http://camel.465427.n5.nabble.com/Why-do-Camel-core-methods-still-throw-Checked-Exceptions-everyone-agrees-they-re-bad-now-right-tp5732364p5732665.html Sent from the Camel - Users mailing list archive at Nabble.com.
