Exceptions

[Nerijus]

Hi, I want to learn more about exceptions. I have an idea to create 2 exception classes:

public class MyError extends Exception {
   public MyError(){   }
}

public class Messages extends MyError {
   public Messages(){   }
}
}

I have other class:

public class Bank {
public int Bank_money;
   public Bank(){   }

public void take_money(int money)throws MyError{
if (Bank_money < money){
throws new MyError();
//And there is error, because this class don't now what  MyError() are
}
}
}

Maybe someone can give me more information about creation of java exception classes? :)

[Norm]

When you get errors, please copy and paste the full text here. Often info in the text will help solve the problem.

Where are the class files located for your new exception classes? Can the compiler find them?

throws new MyError();

"throws" is not a command/statement. See throw.

[Nerijus]

All mine code is really complicated. It have to be throw new MyError();
Thanks, maybe you can give some info about these kind of stuff? :)

[Norm]

For testing out new ideas like these, it's better to start with small and simple programs to get the techniques working. After they are debugged and working, then move them into the larger code.

[Tolls]

Well, I would say an Exception should be called an Exception.
Error is an unchecked type of Exception dealing with serious problems in the system, and you will probably never find a need to actually create one of those.

[RamyaSivakanth]

When you are defining your own exception class

1.Extend the Exception class.

2.Override toString method and give some error message as a string and return it like this below.
public String toString()
{
return " u are wrong";
}

3.In your class under particular method ,if you want to make of ur exception class then,
use throw new MyException() and in throws mention that this method is throwing MyException object using "throws MyException".


4.when u try to call the above method in step 3, automatically ur error message will get displayed.Here toString() will be called on that Object.

[Tolls]

toString() has already been overridden by Throwable, such that it prints the exception name and the message. Overriding it again is pointless.

Add to that that you'd nto generally use toString. Stacktraces are far more useful.

[RamyaSivakanth]

If we want to display our meaningful messages ,then we should override toString() meth.

[Tolls]

Nope, just give the exception a meaningful message.
That's what the message sttribute is for.
There really is no need at all to override toString().