Yes, if you don’t intend to handle or rethrow exceptions, you shouldn’t catch them.
More Related Contents:
- Analyze the following code, which exception does it display? (Exception handling, java)
- Handling InterruptedException in Java
- When to catch java.lang.Error?
- Is it a bad practice to catch Throwable?
- Java 8: Lambda-Streams, Filter by Method with Exception
- Why is the Catch(Exception) almost always a bad Idea?
- Good way to encapsulate Integer.parseInt()
- How do you implement a re-try-catch?
- Spring Boot REST service exception handling
- Increasing heap space in Eclipse: (java.lang.OutOfMemoryError)
- How do I fix a compilation error for unhandled exception on call to Thread.sleep()?
- try with resources introduce unreachable bytecode
- How to loop user input until an integer is inputted?
- Java: Global Exception Handler
- Differences between Runtime/Checked/Unchecked/Error/Exception
- Java if vs. try/catch overhead
- Throws or try-catch
- Mockito How to mock and assert a thrown exception?
- What is a suppressed exception?
- Why can I throw null in Java? [duplicate]
- Java uncaught global exception handler
- What is the advantage of chained exceptions
- What are reasons for Exceptions not to be compatible with throws clauses?
- Why is “throws Exception” necessary when calling a function?
- Guidelines on Exception propagation (in Java)
- Who is calling the Java Thread interrupt() method if I’m not?
- In Java how can I validate a thrown exception with JUnit?
- Why am I getting “must be caught or declared to be thrown” on my program?
- CompletableFuture already completed with an exception
- Is it okay to throw NullPointerException programmatically? [closed]