what happen to the exceptions when try used the finally only instead of catch and how it handles?

Question

when a programmer use a try block without catch

like this

    PersistenceManager pm = PMF.get().getPersistenceManager();
    try {
        pm.makePersistent(c);
    } finally {
        pm.close();
    }

what happen to exception and how it possibly handle later ?

I try learn it from internet but no clear result for it...

for uncaught exceptions: http://www.javamex.com/tutorials/exceptions/exceptions_uncaught_handler.shtml — 9dan, Sep 26 '14 at 07:48
Tutorial, anyone? (In any case, also search for "try-with-resources".) — user2864740, Sep 26 '14 at 07:50

score 1 · Answer 1 · answered Sep 26 '14 at 07:42

1

Yes. It makes sense. In your case even exception comes, the programmer want to just ignore the exception throwed and close the PersistenceManager. At this level the exception ignored and at top level some one may catch that. It delegates to there.

answered Sep 26 '14 at 07:42

Suresh Atta

120,458
37
198
307

score 1 · Answer 2 · answered Sep 26 '14 at 07:43

1

catch statement is used to catch the specific exception based on your need. Even you can use general exception in catch to catch the exception. If you use without catch exception will be handled by default.

answered Sep 26 '14 at 07:43

Shriram

4,343
8
37
64

score 1 · Answer 3 · answered Sep 26 '14 at 07:43

1

At that point the exception is not handled and will still bubble up. It iwll have to be handled later

answered Sep 26 '14 at 07:43

David Pilkington

13,528
3
41
73

score 1 · Accepted Answer · answered Sep 26 '14 at 07:51

When you do not specify a catch block you are basically moving the responsibility of handling the exception to the caller of the method.

So if your method does not catch one or more Exceptions from the try block and an exception is raised in your method block it will be thrown back to the caller.

The finally block ensures that if something bad happens in the try block then at least you will have a chance to close/release any resources related before the exception is thrown back to the caller.

score 1 · Answer 5 · answered Sep 26 '14 at 07:52

This is a common idiom for handling (or better: not handling) exceptions in code that is allocating resources.

If an exception occurs in a try block, this block will end abruptly. Then a corresponding catch statement will be looked up. If this is not found than the outer block will end abruptly, which most of the times means that the method will throw this exception to its caller.

But before that a finally block will always be executed after leaving the try block (and even after handling a caught exception). This is the best place to dispose any allocated resources. In that way you make sure that you clean up after your work, whether an exception occurred or not.

what happen to the exceptions when try used the finally only instead of catch and how it handles?

5 Answers5