Dealing with System Exceptions

Jade raises a number of exceptions automatically. These are known as system exceptions. In Jade, exceptions are implemented as objects.

The following table shows the Exception class of the RootSchema and its subclasses.

Class	Description
Exception	Superclass of all exceptions
FatalError	Serious internal fault
NormalException	Superclass of non-fatal exceptions
ConnectionException	Defines behavior for exceptions that occur as a result of connecting to external systems
FileException	Class of exception raised as a result of file handling
JadeMessagingException	Defines behavior for exceptions that occur when using the Jade messaging framework
JadeSOAPException	Defines behavior for exceptions that occur as a result of web services processing
JadeXMLException	Defines behavior for exceptions that occur as a result of XML processing
ODBCException	Defines behavior for exceptions that occur as a result of connecting to external databases using ODBC
SystemException	Superclass of all exceptions relating to errors detected by the Jade Object Manager
DeadlockException	Exception raised as a result of a deadlock
IntegrityViolation	Exception raised as a result of violating referential integrity rules
LockException	Exception raised as a result of locking conflicts in a multiuser environment
NotificationException	Exception raised as a result of a notification event when the subscriber cannot be found
UserInterfaceException	Class of exception related to handling windows
ActiveXInvokeException	Defines behavior for exceptions that occur as a result of accessing an ActiveX property or invoking an ActiveX method
JadeDotNetInvokeException	Defines behavior for exceptions that occur as a result of accessing a .NET property or invoking a .NET method

You can add further Exception subclasses in your subschemas to create exceptions specific to an application.