[bmckinn8]

I have a method that throws two exceptions. I have a second method that calls the first in the try block. Does this second method need to have "throws Fit" in the method call(like I have it below)? Or, can I omit it.

method 1

public void foo() throws Up, Fit
{
   ...
}

method 2 calls method 1

public void callsFoo() throws Fit
{
     try
     {
          foo();
     }
     catch (Up u)
     {
          ...
     }
     catch (Fit f)
     {
          ...
          throw f;
     }
}

[CasiOo]

You can remove it.

In java you will get a compile error if there is an exception you need to catch but doesnt Unless it is a RuntimeException

[bmckinn8]

Would it be considered a "Good Practice" to leave it in?

[CasiOo]

bmckinn8, on 03 October 2012 - 04:56 PM, said:

Would it be considered a "Good Practice" to leave it in?

If all you do with it is throw it, then I don't see a reason for you to catch it

You are already telling that you are going to throw the exception, so people are aware that it can happen

[jon.kiparsky]

One thing that you'll sometimes see is people catch an Exception, add a note to it, and throw it along, or else wrap it in some other Exception and throw that. This allows you to annotate the stack trace more effectively. For larger applications, this can be useful.

[pbl]

Never seen, or most probably, nver noticed such a practice It might effecticely be uselfull sometimes