catch (FileNotFoundException fileNotFoundException) { log.err(“File was not found” + fileNotFoundException.getStackTrace()); System.err.println(“File was not found” + FileNotFoundException.getStackTrace()”); …3. Inside the catch, return a value that alters the application flow. For example, redirect user to a page “Server temporarily not available”. 4. Do not wrap the whole method in a try and catch block 5. Do not use generic Exception , if more specific exceptions are available. 6. Use method() throws Exception very cautiously and only when there is a very good reason
Try and Catch
1. Never leave an empty catch in a try and catch block: catch (FileNotFoundException fileNotFoundException) { } 2. Output the log:
find similar posts:
Best Practices,
Java
Subscribe to:
Post Comments (Atom)
apt quotation..
“A man should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.” by Robert A. Heinlein (author, aeronautical engineer, and naval officer)
No comments:
Post a Comment