exception class in java

How to define custom exception class in Java, the easiest way?

stackoverflow.com › questions › 3776327 › how-to-define-custom-exception-class-in-java-the-easiest-way

No, you don't "inherit" non-default constructors, you need to define the one taking a String in your class. Typically you use super(message) in your constructor to invoke your parent constructor. For example, like this:

public class MyException extends Exception {
    public MyException(String message) {
        super(message);
    }
}

Answer from djna on Stack Overflow

Stack Overflow

stackoverflow.com › questions › 3776327 › how-to-define-custom-exception-class-in-java-the-easiest-way

How to define custom exception class in Java, the easiest way? - Stack Overflow

Top answer

1 of 8

405

public class MyException extends Exception {
    public MyException(String message) {
        super(message);
    }
}

2 of 8

A typical custom exception I'd define is something like this:

public class CustomException extends Exception {

    public CustomException(String message) {
        super(message);
    }

    public CustomException(String message, Throwable throwable) {
        super(message, throwable);
    }

}

I even create a template using Eclipse so I don't have to write all the stuff over and over again.

Coding Shuttle

codingshuttle.com › java-programming-handbook › class-exception

Class Exception in Java

April 9, 2025 - Java allows developers to create their own exception classes by extending Exception. When built-in exceptions do not represent a specific error scenario in your application.

Discussions

How do you structure your exception classes?

On July 1st, a change to Reddit's API pricing will come into effect. Several developers of commercial third-party apps have announced that this change will compel them to shut down their apps. At least one accessibility-focused non-commercial third party app will continue to be available free of charge. If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options: Limiting your involvement with Reddit, or Temporarily refraining from using Reddit Cancelling your subscription of Reddit Premium as a way to voice your protest. I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns. More on reddit.com

r/java

January 17, 2024

java.lang Exception hierarchy - why?

I have been having trouble understanding the motivation regarding the inheritance hierarchy established with the top level exception classes in java.lang. More specifically, I am wondering why java.lang. RuntimeException (an unchecked exception) has been placed as a subclass to... More on thecodingforums.com

thecodingforums.com

January 10, 2004

Was doing great in Java class until Exceptions. This one stupid thing is gonna make me fail

What's the problem? An exception is just a problem that needs to be handled or else the program will crash. And the exception needs to be handled because exceptions are (typically) thrown in cases where some code has reached an invalid state. If some code doesn't understand how it can resolve the problem, it can throw an exception to request that some "parent" code handle it. Like, say you have a game, and one time when it goes to load the player's save, it finds that there is no save available? It might throw an exception at that point to tell some code higher up in the call chain that it can't handle a problem. It's a way of passing control to some other code that has the context to deal with the problem. Make sure you understand the stack, or understanding what trys handle errors will be impossible for anything nontrivial. More on reddit.com

r/learnprogramming

October 22, 2024

A Throwable other than Error or Exception?

Extending Throwable or Exception (but not RuntimeException) results in a checked exception. Extending Error or RuntimeException results in an unchecked exception. That's the basics. But you really should not extend Throwable. Some absurdly high percentage of code will likely only check for subclasses of Exception. There are... exceptions... obviously. If you have a centralized error handling system, then you may want to catch throwable, and then wrap it in a subclass of Error and log it specially. One thing to note is subclasses of Error. These you can, in your handler, log them or do something lightweight. But you should nearly always re-throw Error. As an example, let's say you are running in Tomcat, and you end up eating ThreadDeathError in your exception handler. Now, the container has no idea that there was an issue with a thread, which can eventually lead to resource leaks and instability. TL/DR: Do not extend Throwable directly, always re-throw Error when encountered. And just my own PoV, avoid checked exceptions when you can. These just add overhead to callers. Most successors to Java have jettisoned checked exceptions, which are not any different in the JVM at runtime in any event from unchecked ones. More on reddit.com

r/java

July 2, 2024

Videos