According to the JDO specification any exception occurring in the context of persistence will be wrapped inside a javax.jdo.JDOException.
The root cause of the exception could be located at the level of the datastore, in the JDO implementation or in the code of the application using the persistence framework. The name of the exception can serve as a first hint as to the nature of the exception:
| Exception | Description |
|---|---|
| JDOUserException,JDOFatalUserException | These are programming or user errors, which can not be handled by Signsoft intelliBO or the datastore. In the case of a JDOUserException you should check the part of the software system you are responsible for, i.e. the code of your application and the mapping descriptions. |
| JDODataStoreException | Exceptions thrown by the datastore which may be resolved by the application (e.g. optimistic locking, constraints). This normally shows problems regarding the datastore, e.g. violation of integrity constraints. |
| JDOFatalDataStoreException | Exceptions thrown by the datastore, which can not be handled (communication failure, network errors). Such exception occurs, if further work in the datastore for some reason has become impossible. This may happen in the case of deceased network connections or wrong user credentials. |
| JDOFatalInternalException | Internal errors thrown by Signsoft intelliBO. If such an exception occurs, it should be reported to the Signsoft intelliBO support (supportteam@intelliBO.com). |
For a complete list of Signsoft intelliBO error codes with short explanations to each of them, please refer to the according part of the documentation.