Access keysTop, Summary, Constructors,
Instance methodsFatalException
| Kind of class: |
class |
| Inherits from: |
AbstractThrowable < Error |
| Implements: |
|
| Known subclasses: |
|
| Author: |
Simon Wacker |
| Classpath: |
org.as2lib.env.except.FatalException |
| File last modified: |
Saturday, 08 October 2005, 19:55:14 |
/*
* Copyright the original author or authors.
*
* Licensed under the MOZILLA PUBLIC LICENSE, Version 1.1 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.mozilla.org/MPL/MPL-1.1.html
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
import org.as2lib.env.except.Throwable;
import org.as2lib.env.except.AbstractThrowable;
/**
* {@code FatalException} is a default implementation of the {@code Throwable}
* interface.
*
* <p>It differs from the {@link Exception} class in that it marks the throwable as
* fatal. That means it differs from a normal {@code Exception} in its fatality.
*
* <p>It also uses the {@code Logger.fatal} method to log itself, while the
* {@code Exception} class uses the {@code Logger.error} method.
*
* <p>Example:
* <code>
* throw new FatalException("This is a detailed message that explains the problem.", this, arguments);
* </code>
*
* <p>The above example is supposed to be in a method, that has been declared on a
* class.
*
* <p>Note that you normally do not throw instances of this class directly. It is
* better to sub-class it, that means to create a custom exception, that explains its
* purpose more closely by its name, and throw this exception instead.
*
* <p>If you are building a framework that shall be reused it is also helpful to built
* a exception inheritance hierarchy, where you have one base class. You can then
* categorize different exceptions by their inheritance hierarchy. This enables you to
* catch all exceptions from your whole framework or only from specific parts of your
* framework.
*
* <p>For a detailed explanation on how to use throwables, what this exception
* framework offers you and how to work appropriately with throwables take a look at
* the class documentation of the {@code Throwable} interface.
*
* @author Simon Wacker
*/
class org.as2lib.env.except.FatalException extends AbstractThrowable implements Throwable {
/**
* Constructs a new {@code FatalException} instance.
*
* <p>All arguments are allowed to be {@code null} or {@code undefined}. But if
* one is, the string representation returned by the {@code toString} method will
* not be complete.
*
* <p>The {@code args} array should be the internal arguments array of the method
* that throws the throwable. The internal arguments array exists in every method
* and contains its parameters, the callee method and the caller method. You can
* refernce it in every method using the name {@code "arguments"}.
*
* @param message the message that describes the problem in detail
* @param thrower the object that declares the method that throws this fatal
* exception
* @param args the arguments of the throwing method
*/
public function FatalException(message:String, thrower, args:Array) {
super (message, thrower, args);
}
/**
* Returns the string representation of this fatal exception.
*
* <p>If you do not call this method out of another method, it also executes the
* {@code fatal} method of the logger returned by the
* {@link AbstractThrowable#getLogger} method passing {@code this} because it thinks
* that the virtual machine called this method.
*
* <p>The string representation is obtained via the invocation of the
* {@link AbstractThrowable#doToString} method that uses the stringifier returned
* by the static {@link AbstractThrowable#getStringifier} method.
*
* <p>If you want to change the appearance of all exceptions set a new stringifier
* via the static {@link AbstractThrowable#setStringifier} method.
*
* <p>If you only want to change the string representation of one exception and
* its sub-classes overwrite the {@code doToString} method in your custom
* exception.
*
* <p>Do not overwrite this method because you will lose the functionality that
* invokes the logger when the exception has not been caught and has now reached
* the final 'level', the virtual machine, that invokes this method.
*
* @return the string representation of this fatal exception
*/
public function toString():String {
if (!arguments.caller) {
if (getLogger().isFatalEnabled()) {
getLogger().fatal(this);
}
}
return doToString();
}
}
FatalException is a default implementation of the Throwable
interface.
It differs from the Exception class in that it marks the throwable as
fatal. That means it differs from a normal Exception in its fatality.
It also uses the Logger.fatal method to log itself, while the
Exception class uses the Logger.error method.
Example:
throw new FatalException("This is a detailed message that explains the problem.", this, arguments);The above example is supposed to be in a method, that has been declared on a
class.
Note that you normally do not throw instances of this class directly. It is
better to sub-class it, that means to create a custom exception, that explains its
purpose more closely by its name, and throw this exception instead.
If you are building a framework that shall be reused it is also helpful to built
a exception inheritance hierarchy, where you have one base class. You can then
categorize different exceptions by their inheritance hierarchy. This enables you to
catch all exceptions from your whole framework or only from specific parts of your
framework.
For a detailed explanation on how to use throwables, what this exception
framework offers you and how to work appropriately with throwables take a look at
the class documentation of the Throwable interface.
Constructor
FatalException
function FatalException (
message:String,
thrower,
args:Array)
Constructs a new
FatalException instance.
All arguments are allowed to be null or undefined. But if
one is, the string representation returned by the toString method will
not be complete.
The args array should be the internal arguments array of the method
that throws the throwable. The internal arguments array exists in every method
and contains its parameters, the callee method and the caller method. You can
refernce it in every method using the name "arguments".
Parameters:
message:
the message that describes the problem in detail
thrower:
the object that declares the method that throws this fatal
exception
args :
the arguments of the throwing method
Instance methods
toString
function toString (
) : String
Returns the string representation of this fatal exception.
If you do not call this method out of another method, it also executes the
fatal method of the logger returned by the
AbstractThrowable.getLogger method passing this because it thinks
that the virtual machine called this method.
The string representation is obtained via the invocation of the
AbstractThrowable.doToString method that uses the stringifier returned
by the static AbstractThrowable.getStringifier method.
If you want to change the appearance of all exceptions set a new stringifier
via the static AbstractThrowable.setStringifier method.
If you only want to change the string representation of one exception and
its sub-classes overwrite the doToString method in your custom
exception.
Do not overwrite this method because you will lose the functionality that
invokes the logger when the exception has not been caught and has now reached
the final 'level', the virtual machine, that invokes this method.
Returns:the string representation of this fatal exception