Not sure I really answer your question, but couldn’t you simply use something like that? public final class SupplierUtils { private SupplierUtils() { } public static <T> Supplier<T> wrap(Callable<T> callable) { return () -> { try { return callable.call(); } catch (RuntimeException e) { throw e; } catch (Exception e) { throw new RuntimeException(e); } … Read more
The simple answer to your question is: You can’t, at least not directly. And it’s not your fault. Oracle messed it up. They cling on the concept of checked exceptions, but inconsistently forgot to take care of checked exceptions when designing the functional interfaces, streams, lambda etc. That’s all grist to the mill of experts … Read more
In Java, as you may know, exceptions can be categorized into two: One that needs the throws clause or must be handled if you don’t specify one and another one that doesn’t. Now, see the following figure: In Java, you can throw anything that extends the Throwable class. However, you don’t need to specify a … Read more
Since I am a new Java developer, I have also faced some difficulties for distinguishing and dealing with different types of exceptions. That is why I have made a short note on this topic, and whenever I get confused I go through it. Here it is with the image of the Throwable class hierarchy: [image … Read more
Thread.sleep can throw an InterruptedException which is a checked exception. All checked exceptions must either be caught and handled or else you must declare that your method can throw it. You need to do this whether or not the exception actually will be thrown. Not declaring a checked exception that your method can throw is … Read more
Unchecked exceptions are those that extend RuntimeException class. Compiler will never force you to catch such exception or force you to declare it in the method using throws keyword. All other exception types (that do not extend RuntimeException) are checked and therefore must be declared to be thrown and/or catched. Checked exceptions are used when … Read more
First things first. This a compilation error not a exception. You should see it at compile time. If you see it in a runtime exception message, that’s probably because you are running some code with compilation errors in it. Go back and fix the compilation errors. Then find and set the setting in your IDE … Read more
I think I read the same Bruce Eckel interview that you did – and it’s always bugged me. In fact, the argument was made by the interviewee (if this is indeed the post you’re talking about) Anders Hejlsberg, the MS genius behind .NET and C#. http://www.artima.com/intv/handcuffs.html Fan though I am of Hejlsberg and his work, … Read more
The simple answer to your question is: You can’t, at least not directly. And it’s not your fault. Oracle messed it up. They cling on the concept of checked exceptions, but inconsistently forgot to take care of checked exceptions when designing the functional interfaces, streams, lambda etc. That’s all grist to the mill of experts … Read more
Checked Exceptions are great, so long as you understand when they should be used. The Java core API fails to follow these rules for SQLException (and sometimes for IOException) which is why they are so terrible. Checked Exceptions should be used for predictable, but unpreventable errors that are reasonable to recover from. Unchecked Exceptions should … Read more