try-catch-finally

Possible Duplicate: Is it possible to detect if an exception occurred before I entered a finally block? I have a workflow method that does things, and throws an exception if an error occurred. I want to add reporting metrics to my workflow. In the finally block below, is there any way to tell if one of the methods in the try/catch block threw an exception ? I could add my own catch/throw code, but would prefer a cleaner solution as this is a pattern I'm reusing across my project. @Override public void workflowExecutor() throws Exception { try { reportStartWorkflow(); doThis(); doThat();

I'm new to Scala continuations, and relatively new to the scala language in general. I tried playing with Scala continuations and wrote the following code: case class MyException(msg:String) extends Exception def go:Int = reset { println("enter your input") val my_check = //try { val user_input = readLine() if (!user_input.matches("\\w+")) { throw new MyException("illegal string: " + user_input) } shift { k: (Boolean => Int) => { if (user_input == "true") { k(true) } else if (user_input == "false") { k(false) } else { // don't even continue 0 } } } } // catch { // case MyException(msg) =>

I'm pretty sure I already know the answer, but I'm still curious what the opinion is on handling an error within a Try,Catch,Finally block -- but when you're repeating yourself. BTW - I'm not talking about User Input - but using that for an example because it is clear and short Consider this bit of code... try { if (success) { return someSuccessMessage; } else { logError("User input not correct format"); return someErrorMessage; // repeats itself } } catch (Exception ex) { logError(ex.Message); return someErrorMessage; // repeats itself } Say we have a function, that if it fails we want to

I am very confused as to why do I need to need to put the clean-up code like closing streams in a finally block. I've read that the code in finally block will run no matter what (whether there's an exception); and after the finally block runs, the rest of the method continues. My question is: if the rest of the method has to continue then why don't I put the clean-up code after my try/catch block in a function? The finally block will always run if an uncaught exception is thrown, but the rest of the code in the method will be skipped. So if you put clean-up code after the finally block, it won

try { FileReader fr = new FileReader(file); BufferedReader br = new BufferedReader(fr); String line = null; } catch (FileNotFoundException fnf) { fnf.printStackTrace(); } finally { fr.close(); } The fr.close() shows an error: fr cannot be resolved I had read that closing a file in the finally block is a good practice. What is that am doing wrong? The variable fr only has scope within the try block. It is out of scope in the finally block. You need to declare it before the try block: FileReader fr = null; try { fr = new FileReader(file); BufferedReader br = new BufferedReader(fr); String line =