Can't java unchecked exceptions be handled using try/catch block?

The only difference between checked and unchecked exceptions is that checked ones have to be either caught or declared in the method signature using throws whereas with unchecked ones this is optional Unchecked Exception can't be handled by your code i.e. We can't use try/catch block Sure we can - but we don't have to Also I think throw keyword can be used only with try/catch block. Can throw Keyword be used with Unchecked Exception?

Note that there are two keywords: throw explicitly throws an exception object you created throw new NullPointerException() works perfectly fine, though explicitly creating that particular exception is uncommon and most would consider it bad style throws declares that a method may throw that exception. With unchecked exceptions this is optional, but can be useful to document the fact (again, one would normally not declared throws NullPointerException because that is pretty much a given).

The only difference between checked and unchecked exceptions is that checked ones have to be either caught or declared in the method signature using throws, whereas with unchecked ones this is optional. Unchecked Exception can't be handled by your code i.e. We can't use try/catch block Sure we can - but we don't have to.

Also I think throw keyword can be used only with try/catch block. Can throw Keyword be used with Unchecked Exception? Note that there are two keywords: throw explicitly throws an exception object you created.

Throw new NullPointerException(); works perfectly fine, though explicitly creating that particular exception is uncommon and most would consider it bad style. Throws declares that a method may throw that exception. With unchecked exceptions this is optional, but can be useful to document the fact (again, one would normally not declared throws NullPointerException because that is pretty much a given).

They can be handled, but you don't have to. If you don't handle them, they will propagate and climb up the calling methods stack, until one of them catches it. If none does, the program will crash.

Usually, the bottom line is that if a client can reasonably be expected to recover from an exception, then it should be a checked exception. If a client cannot do anything to recover from the exception, then it's ok to have it as an unchecked exception. Also, checked exceptions are useful to document an API that you expect to be used by 3rd-parties.

When they know your method can throw a specific exception, they will code accordingly and handle the case. If you only use unchecked exceptions, all bets are off. A common pattern (some people don't like it, but in some cases it's ok when you know what you're doing) is to wrap thrown checked exceptions into unchecked ones.

Try { ... code that can throw CheckedException ... } catch (CheckedException oopsSomethingBadHappened) { throw new RuntimeException("Something bad happened! ", oopsSomethingBadHappened); }.

Yes, you can throw unchecked exceptions with throw. And yes, you can catch unchecked exceptions in a catch block.

You can also propagate them with throws explicitly, which is optional, but can make things clearer in the method signature. – Thilo Nov 12 at 12:31 @Thilo, Hmmm, throws for unchecked exceptions? I can't think of a case where it would be useful... Usually unchecked exceptions are meant NOT to be caught, because they represent programming errors and your program SHOULD crash in this case.

Saying to a client that you expect to throw them would be confusing in my opinion. Which case do you have in mind? – Guillaume Nov 12 at 12:36 The Java SDK API is full of throws IndexOutOfBoundsException and friends.

See download.oracle. Com/javase/1.5.0/docs/api/java/lang/String. Html and also @Michael's answer.

– Thilo Nov 12 at 12:39.

An easy way to think about the difference is to think the checking refers to the compile. If an exception is a checked exception, the compiler will check that your code either throws the exception or handles it in a try/catch block at compile-time. For unchecked exceptions, the compiler won't do such a check.

You can handle checked/unchecked exceptions the same way (with try/catch/throws), the difference just lies in the checks the compiler performs. This post has a decent example.

All the unchecked exceptions can be treated in the same way as the checked ones - if you want, you can let them pass by declaring that the method throws them: public void m() throws RuntimeException {} Or you can catch them: public void m() { try { // some code } catch (RuntimeException re) { // do something } } It should be noticed, the class RuntimeException acts as a catch-all for the unchecked exceptions (since all the unchecked exceptions extend from it), much in the same way that the Exception class is the catch-all for checked exceptions. As has been mentioned before, the only real difference is that for checked exceptions you have to handle them (by letting them pass or catching them) and the compiler will make sure of it - on the other hand, the handling of unchecked exceptions is optional. It all boils down to the expected usage of each exception type - you're supposed do be able to recover from checked exceptions (or at least do something about them, when they occur), whilst for unchecked exceptions, there might not be a reasonable way to recover from them.

This of course, is a bit subjective.

In addition to Guillaume: unchecked exceptions are usually programming errors, which should not happen at all if implemented correctly (index out of bound, null pointer, class cast,...) and therefore the caller/ user usually cannot do anything about them. Checked exceptions are thrown because it was outside of the control of the programmer (network not availabe, filesystem not available, concurrent modifications such as duplicated primary key,...) errors are usually thrown by the JVM and the application usually has to stop (out of memory, stack overflow,...).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.