fido.db
Class FidoException

java.lang.Object
  |
  +--java.lang.Throwable
        |
        +--java.lang.Exception
              |
              +--fido.db.FidoException

All Implemented Interfaces:

java.io.Serializable

Direct Known Subclasses:

ArticleNotFoundException, AttributeCategoryNotFoundException, AttributeNotFoundException, BooleanSyntaxException, CannotDeleteRootObjectException, CannotDeleteSystemLinkException, ClassificationNotFoundException, ClassLinkTypeNotFoundException, FidoDatabaseException, FrameSlotNotFoundException, GrammarLinkNotFoundException, GrammarParseException, InstructionNotFoundException, LeftWallNotFoundException, LookupWordFailedException, MorphologyNotFoundException, MorphologyTagNotFoundException, MultipleEllipsisMatchException, MultipleInstancesMatchException, MultipleMeaningsMatchException, MultipleProperNounsMatchException, NoEllipsisMatchException, NoInstancesMatchException, NoMeaningsMatchException, NoPreviousDiscourseException, NoProperNounsMatchException, ObjectNotFoundException, PrepositionNotFoundException, PronounNotFoundException, ProperNounNotFoundException, QuestionWordNotFoundException, TransactionNotFoundException, UserNotFoundException, VerbInstructionNotFoundException, VerbNotFoundException, WebServiceNotFoundException, WordNotFoundException

public class FidoException

extends java.lang.Exception

Indicates an error occured in the fido server. This is the superclass for all exceptions thrown from the Fido server. This was done because only methods are invoked only two ways:

• From within the FidoServer - if a call fails, there is no way for the software to look at the exception and take corrective action. Therefore all exceptions are treated the same.
• From the DataEditor - from a graphical environment, the message from the server will simply be displayed in a message dialog. No corrective action will be performed from the software, only the user.

Since none of the calling classes will take corrective action, the fact that the call failed is the only information needed. The message will be logged to a file.

The reason to keep each exception its own class instead of every method only throwing FidoException is because internally the server can catch certain exceptions and take corrective action.

See Also:

Serialized Form

Constructor Summary

FidoException()
Constructs an FidoException without a String detail message.

FidoException(java.lang.String s)
Constructs an FidoException with a String detail message.

FidoException(java.lang.Throwable e)
Constructs an FidoException with a nested exception, using that exception's detail message for getMessage().

Methods inherited from class java.lang.Throwable

fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Detail

FidoException

public FidoException()

Constructs an FidoException without a String detail message.

FidoException

public FidoException(java.lang.String s)

Constructs an FidoException with a String detail message.

Parameters:

s - the detail message

FidoException

public FidoException(java.lang.Throwable e)

Constructs an FidoException with a nested exception, using that exception's detail message for getMessage().