|
Exception Summary |
| ClassLoadingException |
A ClassLoadingException can be thrown whenever a Class is supposed to be loaded and
instantiated dynamically with the help of its classname. |
| ComponentException |
A ComponentException is thrown if there are any Component related problems like
unitiated fields or if the Component could not be loaded. |
| ComponentRunnableException |
A ComponentRunnableException exception is thrown if a ComponentRunnable cannot complete
its task successfully. |
| ComponentSupportException |
A ComponentSupportException generally is thrown if there occur any problems related
to the processing of a ComponentSupport object.
It can be thrown, for example, when a ComponentSupport that is specified in a
ComponentChain can't be found or if an appropriate ComponentSupport is present,
but does not work as expected. |
| ComponentWorkerException |
A ComponentWorkerException is thrown if there are any problems related to a special
subclass of ComponentWorker. |
| GUIException |
A GUIException is thrown by GUI components to signal a failure or a problem with
the graphical interface. |
| IllegalModuleException |
An IllegalModuleException can be thrown when an unexpected Module subclass is
passed to a ModuleGroup subclass, i.e. |
| InitiationException |
An InitiationException is only thrown in the initate() method of a Component. |
| MissingDataException |
A MissingDataException can be thrown whenever a certain order or operation cannot be
processed because of insufficient or missing data. |
| RECOINException |
This class forms the superclass for all individual exceptions thrown inside RECOIN. |
| RepositoryException |
A RepositoryException is always thrown in connection with problems while accessing or
manipulating the RECOIN repository. |