Doubt in a Finally block ?

Question

ques 1 :: public class Main {
   public String test() throws Exception
       try
           throw new Exception();
       catch(Exception e)
            throw new Exception();
       finally
    public static void main(String[] args) {
          try{
       new Main().test();
           catch(Exception e)
              e.printStackTrace();
    }According to sun documentation ,a method whose return type is String,int,.. must have return statement otherwise compiler will show an error.But according to this program it will not show any compiler error.Can you please suggest or explain me how this program is compiling.
I have fair idea, that when you throw any exception and after that if u give return statement then it will say its not reachable.
ques 2::
   public String test() throws Exception
       try
           throw new Exception();
       catch(Exception e)
            throw new Exception();
       finally
  return "abc";
    }Again am using same method but here am just returning an value. I want to know what will happen to that new Exception() object which we are throwing at catch block.Since its returning value as "abc".
If you just comment that return statement then it will throw Exception.
Please clarify this also.

Answer 1

My first recommendation is that you build an experiment and see how it behaves. That way you will know without a doubt what to expect based on your coding style. I'm not in any way saying that the behavior is in any way different from what the documentation illustrates, only that if you build a test you'll know for sure. Otherwise, you'll know what we told you and what the documentation says.
Puckstopper's rules #6 - It is preferred to have a single return from any given method. The exception to this rule is if you reach a point in the code that is non-exceptional but creates a condition where the rest of the method should not execute. (There is another rule that relates to this condition that says that in this case the functionality should really be divided because it is clearly overly complex.)
That leads us to a basic code pattern.
int retVal = 0 ; // Initialize to a neutral condition or the default condition
try{
    // Do some stuff that might cause an exception to be thrown
    retVal = RESOLUTION_STATE
// Be specific about exceptions
catch(Exception e){
    // Do something to handle the exception in a graceful and tidy manner.
    // Code that simply barfs the stack trace will incur the wrath of the Exception Gods
finally{
    // Do anything relating to the code in the try and only in the try that must happen no matter what
return retVal ;This does not address the question of whether the exception(s) can or should be handled here. Only a cohesive way of dealing with the try/catch/finally construct and returning from a method.
PS.