Each exception class in its own file????

Question

Hi, I am still quite new to java, and I don't fully understand exceptions. Could you please tell me if for each exception class you require do you have to have a a seperate file. e.g. I'm creating my own array exceptions classes.
The following is the structure:
** The base array exceptions class
public class arrayException extends Exception {
public arrayException () { super(); }
public arrayException (String s) { super(s); }
** The outofboundsArrayException
public class outofboundsArrayException extends arrayException {
public outofboundsArrayException ()
{ super("Number entered is out of bounds"); }
public outofboundsArrayException (String s)
{ super(s); }
** The fullArrayExceptiom
public class fullArrayException extends arrayException {
public fullArrayException ()
{ super("The array is full"); }
public fullArrayException (String s)
{ super(s); }
So will the three classes above need their own file.
I wanted to also know what the super does. I thought when the exception was raised, the text message in the super method is outputted, but i've tested that and it doesn't output (e.g. the error message "The array is full" doesn't output). The only thing that outputs is what you put in the catch part.
Thank You very Much!

Answer 1

Could you please tell me if
for each exception class you require do you have to
have a a seperate file.Yes. Exception classes are like any other public class in Java, in that it must be in its own file with the standard naming conventions.
I wanted to also know what the super does. I thought
when the exception was raised, the text message in
the super method is outputted, but i've tested that
and it doesn't outputsuper([0,]...[n]) calls a constructor in the superclass of your current class matching the signature super([0,]...[n]). In this particular case, the Exception's message property is being set by the parent constructor. If you were to leave out super([0,]...[n]), the default no-arg constructor of the superclass would be invoked, and the message would not be set.
Use the getMessage() method of the Exception class to return the message value in later references to your object.