unchecked-exception

If I have a method which throws an unchecked exception, e.g.: void doSomething(int i) { if (i < 0) throw new IllegalArgumentException("Too small"); // ... } is there any advantage to explicitly declaring that the method throws the exception, i.e. void doSomething(int i) throws IllegalArgumentException { if (i < 0) throw new IllegalArgumentException("Too small"); // ... } as opposed to (or in addition to) describing the behaviour in javadoc: /** * This method does something useful. * @param i some input value * @throws IllegalArgumentException if {@code i < 0} */ void doSomething(int i) { if (i

I have been reading many posts about exceptions lately and I have a question whether unchecked exceptions should be caught. I have read that if you want your application to recover from an error you use checked exceptions. However if you can't deal with the checked exception you either wrap it into another checked exception so you can pass it to another layer; for instance you wrap an SqlException , or you throw an unchecked exception. However, should you catch unchecked exceptions? Are unchecked exceptions ideally programming errors that you don't check for? Should they just bubble up from

In Java, methods that throw checked exceptions ( Exception or its subtypes - IOException, InterruptedException, etc) must declare throws statement: public abstract int read() throws IOException; Methods that do not declare throws statement can't throw checked exceptions. public int read() { // does not compile throw new IOException(); } // Error: unreported exception java.io.IOException; must be caught or declared to be thrown But catching checked exceptions in safe methods is still legal in java: public void safeMethod() { System.out.println("I'm safe"); } public void test() { // method

This was an interview question. What is the main difference between unchecked exception and error as both are not caught? They will terminate the program. Pascal Thivent As stated by their name, unchecked exceptions are not checked at compile-time which means that the compiler doesn't require methods to catch or to specify (with a throws ) them. Classes belonging to this category are detailed in the section 11.2 Compile-Time Checking of Exceptions of the JLS: The unchecked exceptions classes are the class RuntimeException and its subclasses, and the class Error and its subclasses . All other